[Scons-users] Handle updated external dependency files

[Brian Quistorff]

Hi,

Thanks for the response. My projects use mainly Stata, R, Matlab, and
sometimes Python. The analyses read and write intermediate files as well as
produce various files for use by latex in making PDFs. My stats routines
have configuration variables that change which files are read and written.
Those settings are stored in config files or in the code and are manually
changed. A scanner then would be impractical, which is why I usually use my
own dependency generation program (https://github.com/bquistorff/wingendep)
which wraps the stats invocations, tracks file IO, and generates dep files
(like 'gcc -M'). Sometimes I also use latexmk which creates dep files.

After a manual configuration change, running the analyses again may change
the dep files. I would like to avoid two issues, (1) running extra
analyses/simulations that may take a long time (SCons' usage of MD5
signatures helps this a lot in general), and (2) being unsure/forgetful
about invoking SCons multiple times if need be. Because of (1) I would like
the build system to react quickly to changed dep files (no need spending
time on downstream stuff it is going to change). Any help on how do I do
that in SCons?

Cheers, Brian

On Sun, Jul 5, 2015 at 9:28 PM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> Hi Brian,
>
> (Thanks for bringing your query to the users mailing list).
>
> What input effects the contents of the external dependency files?
> Is this input unchanged by the build itself?
>
> Can you mention what software you are using to create the dependency files?
>
> The best way to get a solution is likely not to say "Hey I want to do it
> this way, how do I make that work", but instead say " I need to run these
> tools with these inputs which makes this happen, how do I do that in SCons"
>
> -Bill
>
> On Sun, Jul 5, 2015 at 9:01 PM, Brian Quistorff <bquistorff at gmail.com>
> wrote:
>
>> Hello,
>>
>> I have a some statistical projects where I generate external dependency
>> files and bring them in with ParseDepends. The docs state that multiple
>> invocations of scons may be required when those files are updated in the
>> build, so I usually guess when I have to run it again. It would be nice
>> if scons could detect these updates and do something about it, either by
>> (a) notifying the user, (b) auto-restarting, or (c) updating the DAG. Option
>> (b) seems preferable to assuming it doesn't require much more work. Option
>> (c) would be nice, but seems longer and more complex. Any thoughts on if
>> something is feasible?
>>
>> Thanks,
>> Brian Quistorff
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>>
>
> _______________________________________________
> 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/20150705/6daf9596/attachment.html>