[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Controlling libtool library link stage

From: Too, Justin A.
Subject: Re: Controlling libtool library link stage
Date: Tue, 19 Apr 2011 10:45:51 -0700
User-agent: Microsoft-MacOutlook/

Hi Ralf,

On 4/19/11 10:10 AM, "Ralf Wildenhues" <address@hidden> wrote:

>Hello Justin,
>* Too, Justin A. wrote on Tue, Apr 19, 2011 at 06:52:33PM CEST:
>> The libraries in LIBADD are the convenience libraries generated in
>> subdirectories.  I would like to perform the link step of all of the
>> intermediate libraries into on a ramdisk.
>Why not put the whole build tree on the ram disk?
>I might be spoiled there.

I was initially playing with this idea, but building my src/ directory
alone required ~4.5GB.  I'm trying to enable the ramdisks for Mac OS X
laptops, which currently have a cap of 8GB =(

>> Is there a
>> hook to override's link step such that I can copy all of
>> the intermediate libraries to the ramdisk and then link them into
>> on the ramdisk?
>Not really.
>> Or would I need to create a wrapper for
>> the linker and set the top-level's linker to this
>> wrapper-script?
>You could probably cope without, with something like
># AC_SUBST(ramdisk) adequately from configure.
>libfoo_la_LIBADD = $(ramdisk)/ $(ramdisk)/ ...
># Could use EXTRA_..._DEPENDENCIES with Automake 1.12.
>libfoo_la_DEPENDENCIES = $(libfoo_la_LIBADD)
>$(ramdisk)/ sub/
>        cp -p sub/ $@
>$(ramdisk)/ ...

This should work very well!

Thanks Ralf,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]