Hi Richard, On 21 Apr 2008, at 19:07, Richard Purdie wrote:
gtk+ also has the issues that it tries to run libtool before its been generated and I've had to patch this to run a previously generated version of libtool poky has around to solve cases like this. I'm not sure if there is a neater way to address that problem?
Starting with libtool 2.0, the multipass generation of the libtool
script has been consolidated into a single `config.status' pass, which
happens after all the code in `configure.ac' has completed. The
implication of this is that the libtool script does not exist during
execution of code from `configure.ac', and so obviously it cannot be
called for `--config' details anymore. If you are upgrading projects
that used this idiom to libtool 2.0 or newer, you should replace those
calls with direct references to the equivalent Autoconf shell variables
that are set by the configure time tests before being passed to
`config.status' for inclusion in the generated libtool script.
-- Macro: LT_OUTPUT
By default, the configured `libtool' script is generated by the
call to `AC_OUTPUT' command, and there is rarely any need to use
`libtool' from `configure'. However, sometimes it is necessary to
run configure time compile and link tests using `libtool'. You
can add `LT_OUTPUT' to your `configure.ac' any time after
`LT_INIT' and any `LT_LANG' calls; that done, `libtool' will be
created by a specially generated `config.lt' file, and available
for use in later tests.
Also, when `LT_OUTPUT' is used, for backwards compatibility with
Automake regeneration rules, `config.status' will call `config.lt'
to regenerate `libtool', rather than generating the file itself.
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.redhat.com/autobook
`(_~)_
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
