[Scons-users] optional build components

[Managan, Rob]

Hi,

Section 10.3.2 of the user guide says

As mentioned previously, SCons will normally build every target in or below the current directory by default

So normally it builds all targets below where scons is run. 


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Rob ManaganWCI/DP Division  LLNL
P.O. Box 808, L-095
Livermore, CA  94551-0808
Email: managan1 at llnl.gov


Phone: 925-423-0903         FAX:   925-422-3389

On 1/4/19, 8:55 AM, "Scons-users on behalf of Mats Wichmann" <scons-users-bounces at scons.org on behalf of mats at wichmann.us> wrote:

    
    every time I think I've got a handle on scons I find another way to
    prove I really don't :(
    ...snip ...
    Also struggling with how to see what the default vs. optional targets
    are at a high level, or even the defaults... the material in the SCons
    User Guide on COMMAND_LINE_TARGETS, DEFAULT_TARGETS and BUILD_TARGETS
    looks interesting but seems to not expose anything unless something has
    already happened to set them up - that is, if there have been no
    Default() calls, DEFAULT_TARGETS seems to be empty.  This is not
    intuitive to me - there are still defaults, no?  At some point someone
    added code to our build to store those targets which are the subject of
    installation, such that our help message can dump out those targets,
    essentially a custom internal-install method which includes the line
    
            env.AppendUnique(TS=[name])
    
    that seems kind of awkward but I guess it was done for a reason, since I
    can't currently see a way to extract that info.
    
    Any hints where I can learn more on how to work with this scenario?
    
    
    _______________________________________________
    Scons-users mailing list
    Scons-users at scons.org
    https://pairlist4.pair.net/mailman/listinfo/scons-users