Re: Controlling libtool library link stage

[Too, Justin A.]

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

This should work very well!

Thanks Ralf,
Justin

>
>Cheers,
>Ralf