I just discovered that there's a small wrinkle here... it turns out that scons doesn't use optparse to figure out what's a target and what's not, but instead just ignores things on the command line that start with '-' or contain an '='. So
scons --default FOO build/BAR/m5.debug doesn't work because it thinks FOO is a target. Instead you have to say scons --default=FOO build/BAR/m5.debug --default is the only option this matters for, since the rest are just boolean switches and don't take arguments. Steve On Fri, Mar 4, 2011 at 12:26 AM, Gabe Black <[email protected]> wrote: > After some additional discussion, the original change to update_ref has > been modified, extended, and checked in. The following scons build > variables have been turned into scons command line options: > > default => --default > IGNORE_STYLE => --ignore-style > update_ref => --update-ref > VERBOSE => --verbose > > The rule is now supposed to be that all options that apply only for that > invocation of scons are implemented as command line options, and all > others (which were called "sticky" before) are implemented as scons > variables. Command line options are lower case and use dashes, and SCons > variables are upper case and use underscores. If you find something that > doesn't follow this rule, please let us know. > > Gabe > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >
_______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
