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

site_scons is not respected for Repository #4035

Open
mwichmann opened this issue Oct 18, 2021 · 0 comments
Open

site_scons is not respected for Repository #4035

mwichmann opened this issue Oct 18, 2021 · 0 comments

Comments

@mwichmann
Copy link
Collaborator

mwichmann commented Oct 18, 2021

Filed so the issue is recorded, need to discuss what (if anything) to do about:

If you use a repository (-Y flag or env.Repository call), items from site_scons are not pulled from the repository even if they don't exist in the working directory. A simple thought example is a site_init.py in a repository repo.d that sets a constant FOO to customize the build, have the SConstruct file reference FOO and then invoke scons in an empty directory like:

scons -Y ../repo.d

You'll get an error like:

NameError: name 'FOO' is not defined:
...

This would be the case for SCons itself, which sets constants this way (gzip, git, etc.)

Should scons look for site_init.py in the repository if it didn't find it in the regular site_scons? If so, should it also look for tools in site_scons/site_tools?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant