symlink issue

[bdbaddog]

This issue was originally created at: 2004-10-04 05:56:10. This issue was reported by: issues@scons.

[email protected] said at 2004-10-04 05:56:10

assume the following structure

SConstruct
foo ---> foo-1.0 (symlink)
foo-1.0
   SConscript
   foo.c

Go into the foo directory and call "scons -u".

If SConstruct calls SConscript(os.path.join('foo', 'SConscript')) it says everytime that "scons: 'foo-1.0' is up to date.", which seems wrong to me but on a second look right to scons. ;)

It seems that SCons builds the relative path foo-1.0 and "calls" scons foo-1.0 (which of cause doesn't work either, if called directly) from toplevel. But no one sources the SConscript via "foo-1.0" but via symlink "foo" and therefor its not used for scons and always up-do-date. (Am i wrong?)

Maybe this is fixable using some implicit VariantDir stuff, because if one says VariantDir('foo', 'foo-1.0', duplicate=0) in toplevel SConstruct, it seems to work.

As a workaround a SConstruct or SConscript may source the resolved symlink directly, e.g: SConscript(os.path.join('foo-1.0', 'SConscript'))

Maybe this seems a bit farfetched, but if a SCons build process creates several dir and lib version symlinks, this is an issue.

issues@scons said at 2004-10-04 05:58:59

It seem that some indentation died :/ the structure is:

SConstruct
foo -> "foo-1.0"
foo-1.0/SConscript
foo-1.0/foo.c

issues@scons said at 2004-10-04 05:58:59

Converted from SourceForge tracker item 1039912

gregnoel said at 2008-06-30 17:07:34

Collect all symlink-related issues into a group with the keyword 'symlink'

gregnoel said at 2008-12-26 13:30:38

Adjust triage of issues.

garyo said at 2012-09-01 10:04:01

de-assigning all tickets assigned to Greg Noel (no longer working on SCons)

[mwichmann]

Edited to change BuildDir reference to VariantDir (mostly on behalf of searches)