[Scons-users] Using intermediate build targets inside env.Command()

Managan, Rob managan1 at llnl.gov
Fri Nov 30 15:28:39 EST 2012


There are almost certainly better ways to do this but I would guess that
replacing
"dummysizes $SOURCE $TARGET"
with
dummysizes.abspath + "$SOURCE $TARGET"
might work.




*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Rob Managan email managan at llnl.gov
LLNL phone: 925-423-0903
P.O. Box 808, L-095 FAX: 925-422-3389
Livermore, CA 94551-0808





On 11/30/12 12:21 PM, "Michel Lestrade" <michel.lestrade at crosslight.com>
wrote:


>Hi,

>

>Can anyone explain how to use a build target inside env.Command() ?

>

>In my SConstruct:

> SConscript(dirs='src',variant_dir = 'static64')

>In my SConscript:

> dummysizes = env.Program(target='dummysizes',source = 'dummysizes.c')

> scotch_h = env.Command('scotch.h', 'library.h', "dummysizes $SOURCE

>$TARGET")

>

>However, the command runs as:

> dummysizes static64\library.h static64\scotch.h

>rather than:

> static64\dummysizes static64\library.h static64\scotch.h

>

>How do I change this behavior ? I should have the full path to my

>executable as the output of env.Program() but I cannot seem to use it

>properly.

>_______________________________________________

>Scons-users mailing list

>Scons-users at scons.org

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




More information about the Scons-users mailing list