[Scons-dev] VariantDir source paths in .sonsign.dblite file

[Bill Deegan]

Julian,

What are you trying to do with the information?
BTW. This question is likely more appropriate for the scons-users group as
the dev group is meant for use discussing the development of SCons itself,
and the users mailing list for people building build systems using SCons.

Thanks,
Bill

On Thu, Oct 1, 2015 at 1:12 PM, Rosenthal, Julian <jrosen at qti.qualcomm.com>
wrote:

> Hi,
>
> Quick question regarding VariantDir paths for sources (*.c) stored in
> .sconsign.dblite files.
> I'm very happy to see that dependency info can be retrieved this way.
> Unfortunately, I have a need for the actual source paths rather than the
> VariantDir paths information in my case.
>
> Is there an option for sconsign to output this information with actual
> source paths?
> Is there a way to convert this information back to actual source paths
> (after the fact)?
> I can see how I could convert this back knowing what VARIANTDIR is, but
> even then I have to make some assumptions as to the actual source path.
> (<PARTIAL SOURCE PATH> versus <SOURCE PATH> in the example below)
>
> Example:
> Following information is available in sconsign for an example source file:
> <BUILD_ROOT>/<PARTIAL SOURCE PATH>/<VARIANTDIR>/<SOURCE FILE>
>
> I need the info to be the following:
> <BUILD_ROOT>/<SOURCE PATH>/<SOURCE FILE>
>
> I need the location of the source file (*.c) before it is copied to
> VARIANTDIR.
>
> Thx for any pointers.
>
> Sincerely,
>         Julian Rosenthal
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20151001/b243fa5e/attachment.html>