Location:this issue page
Many users current set the environment variable SCONSFLAGS to automatically include certain command-line arguments when running SCons. This environment variable affects all SCons scripts, however, not just those written with our sconsUtils package, and most users who set SCONSFLAGS typically include sconsUtils-specific options. This causes problems when building packages that use SCons without sconsUtils (such as GalSim, or, at least until
Instead, sconsUtils read a new environment variable for sconsUtils-specific options; I'm proposing we call that SCONSUTILSFLAGS (though the lack of word separators is annoying, that seems most analogous with SCONSFLAGS). When this is available, users should use this new environment variable for sconsUtils-specific options like "opt=3", while continuing to use SCONSFLAGS for generic options like "-j4".