I just merged Rob's pull request last night, so yes this should all be
working now (at least as designed). I'll tell Eric.
On Fri, Dec 21, 2012 at 10:37 AM, Russel Winder rus...@winder.org.ukwrote:
I am guessing this is now fixed – I merged mainline/default/tip and the
Aeryn build works
Rob,
I have a SCons build and install of a shared and static library that I
can run on Linux and OS X, would it help to try this? The proble, is I
have a whole load of hacks in there to do all the symbolic link and
soname creation, so wopuld need a little guidance as to what is done in
the new
PS. In the example I sent you will need to change the install path since I
hard wired one on my system just for testing purposes.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Rob Managan email managan at llnl.gov
LLNL phone:
Rob,
Just to note. I merged your Soname fork into my D Tooling fork and no
problems. So I tried to clean my directory and got:
| scons -c .
/usr/bin/python
/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling_SOName/bootstrap/src/script/scons.py
-c .
scons: Reading SConscript
Russel,
The messages like
SHLIBVERSION '' does not match the version # '2.1.2' in the filename,
proceeding based on file name
are in some sense development warnings that we may remove. It comes from
install.py checking that the version number in the file name matches the
SHLIBVERSION defined in
Rob,
Your project on Debian Unstable with a change of installation directory
gives me:
lrwxrwxrwx1 russel russel16 Nov 7 18:10 libtest.so -
libtest.so.2.5.4*
lrwxrwxrwx1 russel russel16 Nov 7 18:10 libtest.so.2 -
libtest.so.2.5.4*
lrwxrwxrwx1 russel russel16 Nov 7
Rob,
OK, I almost got my library build working. Current big problem is that
the symbolic links are created in the SCons execution directory not in
the build directory.
--
Russel.
=
Dr Russel Winder t: +44 20 7585
Ah,
I had not tried it with a variantDir setting. I need to look into that to
make sure I get the paths correct!
Thanks for pointing that out.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Rob Managan email managan at llnl.gov
LLNL
On Wed, 2012-11-07 at 19:30 +, Managan, Rob wrote:
Ah,
I had not tried it with a variantDir setting. I need to look into that to
make sure I get the paths correct!
Thanks for pointing that out.
No worries.
If I manually hack in the links it all seems to work as expected.
It means I
For those that are interested I have another update to the repo at
https://bitbucket.org/managan/scons_soname .
I have a first cut at support for the Install commands and started cleaning up
and encapsulating stuff in _init_.py and link.py.
I am working on adding a test case and having to wrap
...@scons.org [scons-dev-boun...@scons.org] on behalf of
William Deegan [b...@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 ch...@behanna.org
On Oct 25, 2012, at 19:33 , William Deegan b...@baddogconsulting.com wrote:
All,
On Oct 25, 2012, at 1:16 PM, Chris BeHanna ch...@behanna.org wrote:
On Oct 25, 2012, at 15:07 , Managan, Rob manag...@llnl.gov wrote:
Hi Chris,
Thanks for the info. Sounds like I should have the Install
On Fri, Oct 26, 2012 at 11:29 AM, Chris BeHanna ch...@behanna.org wrote:
On Oct 25, 2012, at 19:33 , William Deegan b...@baddogconsulting.com
wrote:
All,
On Oct 25, 2012, at 1:16 PM, Chris BeHanna ch...@behanna.org wrote:
On Oct 25, 2012, at 15:07 , Managan, Rob manag...@llnl.gov
At the moment this is sets link flags for posix, cygwin, and darwin. Names and
symlinks are set for posix and darwin.
My testing at the moment is limited to generating a shared library. I suppose I
could add a test that links against it if that is sufficient.
Given what needs to be done for
Hi Rob,
just had a quick look at your changes...thanks a lot for taking care of
this issue.
On 25.10.2012 06:09, Managan, Rob wrote:
I want to get some input on this issue. I created a fork for this at
https://bitbucket.org/managan/scons_soname and put Eric Raymond's code
into
Bill and Dirk,
I think I tend to agree with Bill that Install should not surprise the user.
For ease of finding the functionality I will look at adding
InstallVersionedLibrary so it naturally sorts along with Install and InstallAs.
I suppose I can try to make it smart enough to figure out if
On Oct 25, 2012, at 14:42 , Managan, Rob manag...@llnl.gov wrote:
Bill and Dirk,
I think I tend to agree with Bill that Install should not surprise the user.
For ease of finding the functionality I will look at adding
InstallVersionedLibrary so it naturally sorts along with Install and
On Oct 25, 2012, at 15:07 , Managan, Rob manag...@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
All,
On Oct 25, 2012, at 1:16 PM, Chris BeHanna ch...@behanna.org wrote:
On Oct 25, 2012, at 15:07 , Managan, Rob manag...@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
19 matches
Mail list logo
