Re: Is it possible to obtain the real file path in SCONS generated dblite file?

Praveen Singh Chetpet <[email protected]>
Newsgroups gmane.comp.programming.tools.scons.user
Message-ID <[email protected]>
Thanks Bill. I will try the suggested solution.

Regards,
Praveen

From: Scons-users <[email protected]> On Behalf Of Bill Deegan
Sent: Friday, March 29, 2019 10:19 PM
To: SCons users mailing list <[email protected]>
Subject: [EXT] Re: [Scons-users] Is it possible to obtain the real file path in SCONS generated dblite file?

Praveen,

Look at the manpage search for "${SOURCE.srcpath}" for the section on doing interesting things with SOURCE and TARGET.
https://scons.org/doc/production/HTML/scons-man.html

Does this answer your question?
-Bill

On Thu, Mar 28, 2019 at 7:30 PM Praveen Singh Chetpet <[email protected]<mailto:[email protected]>> wrote:
Hi,

We use Variant Dir Feature from SCONS to build the object files and libraries in a different directory than where the source is located.
When we do this, SCons reports the source files as if they existed in the object/library directory rather than in the source directory.


Earlier my senior colleague Don has spent some time trying to get the sconsign tool to tell us the source directory, and tried other ways to check SCons implementation itself to see if we can find that information at build time, but haven’t found anything concrete.

Could you please help us on obtaining the actual source directory rather than the place from where it is being compiled during build time, or please suggest if there is any other way?

Thanks,
Praveen
_______________________________________________
Scons-users mailing list
[email protected]<mailto:[email protected]>
https://pairlist4.pair.net/mailman/listinfo/scons-users

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.