[Scons-users] ParseDepends and duplicate with variant directories

Bill Deegan bill at baddogconsulting.com
Sun Dec 17 21:09:44 EST 2017


Hmm... you might be able to provide the compiler with the source directory
for each variantdir path?

Look at the manpage and search for:
http://scons.org/doc/production/HTML/scons-man.html

rsrcdir or rsrcpath

That should work.
You'll have to do something similar to _concat, but to replace the values
with the .rsrcpath.

Then you may have to transpose those back to the variant dir paths
depending if you expect the variantdir to have generated header files or
not..



On Sun, Dec 17, 2017 at 1:57 PM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> Any logic in the wiki is community supported.
> You might consider contributing your logic to the scons-contrib repo.
>
> The copying of files is only true with variant dir if duplicate = 1.
> If duplicate =0, then they are not copied.
>
> It's probably simpler to get such to work in the case where duplicate=0.
>
> That said (as you can see) the implementation in the wiki is not
> "production ready" for all scons usages, so the rest is an exercise for the
> user.
>
> You might consider picking up the pull request still on bitbucket for a
> more complete C scanner implementation which does much of the preprocessor
> logic.
>
> What's driving you to use the compiler itself to generate the dependencies?
>
> On Sun, Dec 17, 2017 at 8:25 AM, Gaurav Juvekar <gauravjuvekar at gmail.com>
> wrote:
>
>> Hi,
>>
>> I'm using this (https://bitbucket.org/scons/scons/wiki/ParseDepends) to
>> use the compiler generated dependencies without requiring two passes.
>> However, the problem is that when using it with variant directories, SCons
>> first copies over the files that it detects a dependencies using the
>> internal scanner, and then the compiler is run (in the variant dir) to
>> generate dependencies which fails if some required files weren't found by
>> the SCons scanner, defeating the point of using ParseDepends in the first
>> place.
>>
>>
>> Is there a way to get the ParseDepends Builder to run in the source
>> directory, and then copy over all of the compiler generated dependencies.
>>
>>
>>
>> ParseDepends implemented as a tool https://gist.github.com/gaurav
>> juvekar/9aed8d1ac117dc30ef34b28f4933e192
>>
>> --
>> Regards,
>> Gaurav Juvekar
>>
>> _______________________________________________
>> 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/20171217/f5e3b511/attachment.html>


More information about the Scons-users mailing list