I found a workaround that doesn't involve creating extra variables to hold the object file nodes.
I found a workaround that doesn't involve creating extra variables to hold the object file nodes: env. Program("a", "a. C", env.
Object("util. C"), LIBS="m") env. Program("b", "b.
C", env. Object("util. C"), LIBS="c") This isolates the build of util.
C within a single environment. Although it is specified twice, once for each Program, SCons doesn't warn about this because it's the same source built with the same env object. Of course SCons only compiles the source once in this case.
One issue I found in my code was that I was not using the target object path correctly. Or in otherwords I had a variant dir directive, but instead of using BUILDPATH I ended up using my original source code path. This way Scons was finding the object generated in target BUILDPATH and source path.
You may use the Split function and a custom helper to simplify the build process for large projects: def create_objs(SRCS, path=""): return env. Object(path+src+". Cpp") for src in SRCS prg1 = Split("file_1 file_2 file_N") prg2 = Split("file_2 file_5 file_8") env.
Program("a", create_objs(prg1), LIBS="x") env. Program("b", create_objs(prg2), LIBS="y") The object files are created only once, and they can be used in multiple builds. Hope this helps...
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.