[Scons-users] Pulling information out of sconsign

[Bill Deegan]

env['SPAWN']...

running -j # may screw up your output..

-Bill

On Tue, May 17, 2016 at 10:35 AM, Fred Wright <fw at fwright.net> wrote:

>
> On Tue, 17 May 2016, Evan Driscoll wrote:
>
> > On 2016-05-17 02:35, Tom Tanner (BLOOMBERG/ LONDON) wrote:
> > > Sadly scons doesn't store the fully expanded command line inside the
> > > .sconsign file. I actually did this where I work and the changes are
> > > small but increases the size of the file hugely, and it should be
> > > noted that it doesn't make so much sense for commands that are
> > > actually python functions.
> >
> > That's too bad; I guess I'll see if I can figure out another way. Maybe
> > 'scons |& grep gcc > commands.txt' :-).
>
> If scons always uses the same Python function(s) to execute external
> commands, you could just install a wrapper around that function(s) to
> capture the commands (and even the environment).  Depending on where it
> fits in, it may or may not need to worry about parallelism for -j.
>
> Fred Wright
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20160517/73287106/attachment.html>