[Scons-users] Changes in linker options don't rebuild SharedLibrary

Jason Swager jswager at alohaoi.com
Tue Dec 17 10:15:38 EST 2013

Thanks for the update. I was getting rather worried because I was pretty
sure that this sort of thing worked in earlier versions of SCONS.

Any idea when SCons 2.4 might be released (assuming it includes the fix)?
Although I personally have no problem switching to a dev version of SCons,
I'm going to face some pressure when I try to use that in the rest of our
dev organization. Having an "official" release would make the introduction
much more smooth.
Thanks for the quick responses!

On Tue, Dec 17, 2013 at 5:51 AM, Gary Oberbrunner <garyo at oberbrunner.com>wrote:

> Yes, this is a known issue in 2.3.0. It is fixed in the default branch in

> bitbucket.



> On Mon, Dec 16, 2013 at 4:50 PM, Jason Swager <jswager at alohaoi.com> wrote:


>> Hello,

>> I've encountered what seems to be a rather serious problem in SCONS

>> linking. I'm hoping that I'm just doing something stupid or misconfigured

>> something, but something seems wrong. What I'm finding is that changing

>> the linking options won't cause a rebuild of a shared library if it has

>> already been built. Here are the details of the my situation...


>> SCons 2.3. Visual Studio 2010. Windows 7 64bit machine.


>> The DLL I'm compiling is REAL simple (SomeDLL.cpp):


>> int hello()

>> {

>> return 0;

>> }


>> The SConstruct is also very simple:


>> env=Environment(tools=['default'], MSVC_VERSION='10.0', TARGET_ARCH =

>> 'x86', no_import_lib='1')

>> env.AppendUnique(SHLINKFLAGS=['/FORCE']) #

>> env.SharedLibrary(target='SomeDLL.dll', source=['SomeDLL.cpp'])


>> Running this once, the DLL gets built. Run it a second time, nothing

>> gets built because nothing has changed. If I comment out the second line

>> (the SHLINKFLAGS modification), then run "scons" again, nothing gets

>> rebuilt. Adding/removing that line should have caused a relink.


>> I also tried changing LINKFLAGS and even LIBS, but modifications to those

>> construction variables didn't cause a relink.


>> Just for reference, changes to compilation flags CXXFLAGS, CPPPATH,

>> CCFLAGS would cause a rebuild of the CPP file, resulting in a relink of the

>> DLL. But changes to the linker options seem to be ignored.


>> Am I doing something wrong?

>> Thanks,

>> Jason Swager


>> _______________________________________________

>> Scons-users mailing list

>> Scons-users at scons.org

>> http://four.pairlist.net/mailman/listinfo/scons-users





> --

> Gary


> _______________________________________________

> Scons-users mailing list

> Scons-users at scons.org

> http://four.pairlist.net/mailman/listinfo/scons-users



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://four.pairlist.net/pipermail/scons-users/attachments/20131217/d219eac6/attachment.htm

More information about the Scons-users mailing list