No description provided.
Make use of system search path, so distributed software is supported …
I don't understand. LLVM_ROOT should be set by the user to the right path, so this should not be needed?
This is not needed - but still possible. Most people (like me) will install the distributed software which installs to some path included in PATH. So why should they have to jump to loops and manually assign the path, when it can be taken from the os.
On the other hand due to the override path in which, if you want to force the locating to use a special path/version, you still can.
And above all it checks for the existance of the binaries so there is no invalid path set.
Make the default for program building _html_
Merge branch 'incoming' of https://github.com/kripken/emscripten into…
Ok, I see. It does make sense to make this as simple as possible. However this is tricky stuff so we should not land it without tests. Tests should probably go in sanity since they will need to modify ~/.emscripten I assume.
Is the change to scons a separate issue?
I don't see any scons changes here, perhaps they were part of #448?
Could be, yeah.
Ok, then what is left is the stuff we need tests for, before merging.
Closing as no steps to get this integrated are named.
The comment before yours says that we need tests to merge this. Was that not specific enough?
What kind of tests? Tests for what?
Ordinarily if all present tests succeed, I would assume that the paths are processed correctly.
It would be good to actually test the new functionality here, that the system path is checked. But I guess we can include this if nothing is broken in current tests.
Aside from 4. you did mention no additional test/concerns!?
As for tests, like I said, I would really like tests for this new functionality. But not mandatory for merging, assuming you see it breaks nothing and the new functionality works for you locally. So let's finish this pull.
Hmm, I did just have one concern just now. Let's show a warning in debug mode (EM_DEBUG variable is true in tools/shared.py) when a system path is used. That way if someone gets odd behavior, and try debug mode, they will see which path is used (so if they have some old version of llvm in their path, they will be told). Or perhaps in debug mode we should print out the paths as they are used, system or no?
I think we can close this, given the amount of time since last activity?