-
Notifications
You must be signed in to change notification settings - Fork 423
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
find used variables doesn't consider short-circuiting #3255
Comments
Known issue. Conda build would have to parse, not just pattern match. It would be a large increase in complexity. PRs definitely welcome here if you have good ideas on how to do this without too much work. It would be a big improvement, but it's not one that we have time to do ourselves right now. |
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
Let's keep this open |
Actual Behavior
If I have
# [osx and c_compiler == 'toolchain_c']
, then conda-build thinksc_compiler
is used in windows as well.Expected Behavior
c_compiler
not in used variables in windows.Steps to Reproduce
example recipe: conda-forge/r-base-feedstock#61
Using conda-build 3.16.2
The text was updated successfully, but these errors were encountered: