> > The problem is that a libtool .so file, AFAIK, is not the same as a
> > regular .so file.
> 
> It is the same as a .so file:
> 
> [EMAIL PROTECTED] apr-util]$ file .libs/libaprutil.so.0.0.0
> .libs/libaprutil.so.0.0.0: ELF 32-bit LSB shared object, Intel 80386, version 
> 1, not stripped
> [EMAIL PROTECTED] apr-util]$
> 
> > It is a hack so that the same thing works on all
> > platforms.
> 
> They do a bunch of stuff to get shared libs working wherever possible. On
> platforms that don't support them at all, then some magic occurs. Don't ask
> me what because I haven't seen that (because those platforms are relatively
> rare nowadays). The libtool manual probably describes this well.
> 
> > I do not believe that libtool .so files work when the program
> > using them is not using libtool, so this would limit apr-utils usefulness
> > to just programs using libtool.  I would much prefer to not have that
> > limitation.
> 
> Nope. The .so files are standard .so files. Anybody can use and link against
> them, just like every other .so file.

Okay, my comments came from reading the libtool manual, but if you have
real-world experience with this, lets just use libtool.

Ryan


_______________________________________________________________________________
Ryan Bloom                              [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------

Reply via email to