I've done this before, just a sec...
(some googling)
I think you have to use an Action object instead of a raw command in
the Command builder. When building the Action object, the second
parameter is the alternative text to output.
It might look like the following:
env.Command(target, source, Action("foo $TARGET $SOURCES", "FOOING $SOURCES"))
The []s are probably not necessary, but that's just my opinion.
It might be better to support a -v or --verbose option on the scons
command line if we can. An environment variable is a little obscure,
and it's likely you'll just want verbose output temporarily, not as a
long term environment setting. I don't really remember whether adding
command line options to the scons command line is feasible and/or
advisable, so I'll defer to other people's opinions, but it seems a
little more natural to me.
Gabe
Quoting Ali Saidi <[email protected]>:
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/299/
-----------------------------------------------------------
(Updated 2010-11-08 15:49:05.987230)
Review request for Default.
Summary (updated)
-------
Scons: Try to make SCons output prettier.
This change has scons print [ C], [CC], [LN], etc in front of normal
commands instead of the entire command themselves and cleans up the
build a good bit. Unfortunately, I couldn't figure out a way to get
the same behavior from env.Command() calls so they're still verbose.
Thoughts? Like it? Hate it?
Diffs
-----
SConstruct f61e079ad05e
Diff: http://reviews.m5sim.org/r/299/diff
Testing
-------
Thanks,
Ali
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev
