[Scons-dev] Issue 2869 - Versioned shared libraries

[Managan, Rob]

Bill,

It claims to but I can't say I have done more than test the mechanics. That is, it generates the link flags separately for posix and darwin, and names the files and symlinks separately as specified in Eric Raymond's functions.
________________________________________
From: scons-dev-bounces at scons.org [scons-dev-bounces at scons.org] on behalf of William Deegan [bill at baddogconsulting.com]
Sent: Thursday, October 25, 2012 5:33 PM
To: SCons developer list
Subject: Re: [Scons-dev] Issue 2869 - Versioned shared libraries

All,
On Oct 25, 2012, at 1:16 PM, Chris BeHanna <chris at behanna.org> wrote:


> On Oct 25, 2012, at 15:07 , "Managan, Rob" <managan1 at llnl.gov> wrote:

>

>> Hi Chris,

>>

>> Thanks for the info. Sounds like I should have the Install function check

>> that the version numbers match. In the use case where Install does not

>> know what the version number is then I will believe the one in the library

>> name!

>>

>> Of course, in the example from Eric Raymond on OSX there is only one

>> symlink and the version number is located differently.

>

>       Yes, it's very, very different on OS X.  OS X uses "Mach-O" format rather than ELF, and spells ".so" as ".dylib", plus it reverses the order of the version number and the file type suffix:

>

>       libcurl.so.4 => libcurl.4.dylib

>

> Mach-O also uses a "compatibility version" that is distinct from the version that appears in the filename.  :-/


Does the implementation work with both linux and OSX?

-Bill
_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev