[Scons-users] Creation of an archive of source files with Node.all_children()

Dirk Bächle tshortik at gmx.de
Tue Jan 20 13:18:47 EST 2015


Paul,

On 20.01.2015 06:01, Paul Grégoire wrote:
> Hi Dirk,
>
> Thank you, your answer makes sense for me, and I realise I never noticed that scanners are called during the compilation phase and
> not during the analysis phase.
>
> So, to solve my problem, I do not imagine a clean solution now. My last idea is to use the result of the --tree option. Using scons
> --tree=prune, perhaps with --dry-run to get the complete list of dependencies, and then post process this output with an external
> script to create the archive. I will try to create such a script. Could you tell me if it is simple to add an option to the --tree
> option to obtain an output that will be simpler to parse with a script ? If it is not simple, I will do the job with one of the
> existing output.
>

I'd probably not bother to mess with the way SCons outputs its dependencies. There are already some starting points for your script, 
see:

   https://el-tramo.be/blog/scons2ninja/
   http://www.scons.org/wiki/SconsTreeView

Best regards,

Dirk



More information about the Scons-users mailing list