On 2006-04-13, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * Olly Betts wrote on Thu, Apr 13, 2006 at 05:29:26PM CEST:
>> I realise that there is in general (both for libraries and modules), but
>> when building modules for a particular application that is known not to
>> ever use .la files there isn't, is there?
>
> Hmm. Rather for documentation purposes then, I guess.
I think that's a bit of a reach!
>> In fact, for this use case what you probably want to be able to say to
>> libtool is "build me only a shared module (and fail if you can't) and
>> create it in the current directory (skipping the usually .la wrapper
>> with the .so in the .libs subdirectory)".
>
> Yes, but this would make the build machinery much more complicated.
Fair enough. It's not annoyed me enough to complain until you
explicitly asked!
> But I think you could be using
> $LIBTOOL --mode=execute -dlopen modules/module1.la \
> $(PHP) -c php.ini ...
That's definitely better.
> instead. Except for the small design bug with execute mode, that if
> you have the installed module dir as RPATH, then it's system-dependent
> whether libtool can actually override that with $shlibpath_var. But
> if you don't do that, this should be fine.
How do I check PHP's RPATH?
Cheers,
Olly
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
