Hi Paolo,
On 10 Jun 2010, at 11:07, Gary V. Vaughan wrote:
> On 10 Jun 2010, at 08:18, Paolo Bonzini wrote:
>> On 06/09/2010 04:46 PM, Gary V. Vaughan wrote:
>>> Why so much cruft in ltmain.m4sh just to drive a different archiver? It
>>> seems to me that this would be better and easier to maintain, test and
>>> extend
>>> as a whole new script. Let's call it, $prefix/libexec/libtool/ar, build it
>>> from $srcdir/libltdl/config/ar.m4sh, and have libtool set AR to point at the
>>> script instead of /usr/bin/ar when the system is funky.
>>
>> What about embedded libtool, which is really the common case?
>
> What is "embedded libtool"? For cross-compiling to underspecified embedded
> systems?
D'oh. You mean building and running libtool inside the calling project.
Good point.
There are 2 easy ways to accomodate:
i) have the ar wrapper figure out at run-time what it needs to do, and
leave it in $auxdir ($top_srcdir/build-aux for most projects, but in
the libtool distro = $top_srcdir/libltdl/config), and uninstalled
libtool will call it from there.
ii) have configure figure out what the wrapper needs to do, and build it
in $builddir (alongside the libtool script). Uninstalled libtool will
call it from there.
Cheers,
--
Gary V. Vaughan (g...@gnu.org)
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
