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

Display available tools #1007

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

Display available tools #1007

bdbaddog opened this issue Jan 2, 2018 · 0 comments

Comments

@bdbaddog
Copy link
Contributor

bdbaddog commented Jan 2, 2018

This issue was originally created at: 2004-11-10 08:31:15.
This issue was reported by: mdoar.
mdoar said at 2004-11-10 08:31:15

A common problem people seem to run into is:

AttributeError: SConsEnvironment instance has no attribute 'Java':

when they try to use a particular tool, Java in this case. I understand that this is because when the SCons looked for the various tools, and it didn't find this one. The problem is that the error message doesn't give any clue about making sure that Java is found on the path.

One solution might be to have a --debug=env option to display the environment that SCons found. This would be more that DumpEnv, since it could show where it looked for the various tools, what it tried to run to determine if each tool was working and so on.

~Matt

issues@scons said at 2004-11-10 08:31:15

Converted from SourceForge tracker item 1063929

garyo said at 2008-03-17 20:22:15

dup of 1671

*** This issue has been marked as a duplicate of 1671 ***

Votes for this issue: 1.

garyo said this issue is a duplicate of #1671 at 2008-03-17 20:22:15.

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

No branches or pull requests

2 participants