Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variables('custom.py') should read from source directory #816

Open
bdbaddog opened this issue Jan 2, 2018 · 0 comments
Open

Variables('custom.py') should read from source directory #816

bdbaddog opened this issue Jan 2, 2018 · 0 comments
Labels

Comments

@bdbaddog
Copy link
Contributor

@bdbaddog bdbaddog commented Jan 2, 2018

This issue was originally created at: 2004-05-16 01:58:01.
This issue was reported by: issues@scons.
issues@scons said at 2004-05-16 01:58:01

Currently, the custom.py in Options('custom.py') was reading from the build directory. If the build directory and the source directory are not the same, the custom.py put in the source directory will not be read.

Is this behavior intensional? opts.Save('opts.cache') also save the options in the build directory.

issues@scons said at 2004-05-16 01:58:01

Converted from SourceForge tracker item 954759

gregnoel said at 2009-04-30 15:29:02

Bug party triage. The Variables (formerly Options, I changed the summary to match) code is still opening the file by hand rather than using the File() infrastructure (e.g., get_text_contents()). It should be simple fix so mark it +Easy; maybe someone else can do it.

@bdbaddog bdbaddog added this to the 2.x milestone Jan 2, 2018
@mwichmann mwichmann removed this from the 2.x milestone Mar 26, 2021
@mwichmann mwichmann added the Variables label Apr 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants