Re: [Log4cplus-devel] log4cplus SO file - forcing the SONAME header field

[Václav Z. <vha...@gm...>]

On 05/23/2013 03:25 PM, Brice Copy wrote:
> Hello,
Hi.

> 
>  
> 
> I am compiling log4cplus from source on Red Hat enterprise 5 (CERN
> scientific linux) 32 and 64 bits.
> 
>  
> 
> The point is to package Log4cplus in my Java webstart project (to enable
> logging in a native C++ library).
> 
>  
> 
> The problem is that when I use the configure and make scripts, it
> produces a liblog4cplus-1.1.so.5 library file.
> 
>  
> 
> I really need the library file that ends with “.so”  - or Java webstart
> will not unpack it from the native library JAR package and add it to the
> library path.
> 
>  
> 
> Renaming the file to liblog4cplus-1.1.so does not work, because I link
> my own native library to log4cplus, and the liblog4cplus-1.1.so.5 file
> contains the SONAME set to “liblog4cplus-1.1.so.5” (so the linker will
> link to liblog4cplus-1.1.so but my own library expects
> liblog4cplus-1.1.so.5 to be present on the path).
> 
>  
> 
> Is there a “configure” option I can use to force the SONAME to
> liblog4cplus-1.1.so ?
> 
> Or can I strip the SONAME from the final library, thereby forcing the
> linker to link to the library file name liblog4cplus-1.1.so ?
I am attaching a patch (now part of both trunk and 1.1.x branch) that
should allow you to configure log4cplus with --disable-so-version and
--disable-release-version flags. The produces shared library is
liblog4cplus.so (on Ubuntu). HTH.

-- 
VZ