[TIMOB-5821] Android SDK r14 tooling breaks scons
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2012-03-06T15:46:55.000+0000 |
Affected Version/s | Release 1.7.3 |
Fix Version/s | Sprint 2011-43 |
Components | Tooling |
Labels | n/a |
Reporter | Eric Merriman |
Assignee | Bill Dawson |
Created | 2011-10-20T17:22:24.000+0000 |
Updated | 2017-03-07T23:59:58.000+0000 |
Description
Description:
While setting up our new QE team members, we encountered a problem with scons failing. After speaking with Don, this is caused by the naming convention used for new installations for the API 7 folder in /add-ons. Details of the console output are:
Traceback (most recent call last):
File "/usr/local/bin/scons", line 5, in
pkg_resources.run_script('scons==2.1.0', 'scons')
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 489, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 1207, in run_script
execfile(script_filename, namespace, namespace)
File "/Library/Python/2.7/site-packages/scons-2.1.0-py2.7.egg/EGG-INFO/scripts/scons", line 187, in
import SCons.Script
ImportError: No module named SCons.Script
Steps to reproduce:
1) Perform a clean installation of the Android SDK API 14
2) In terminal go to your titanium_mobile GIT repository
3) try to scons
Result:
scons fails with console error as listed above
Expected:
scons completes successfully
This error looks like a SCons installation issue, is there something else related to Android r14 that you were seeing?
I have r15 (it just came out) and cannot reproduce this on OSX *10.6.8*. Is this still reproducible? The error message looks more like a scons configuration problem than anything to do with Android tools revisions.
We will check if this is still reproducible. The issue was with new installations only. If you previously had the SDK installed, the update would work fine. If you didn't, the fresh install would fail. w
Need QE to verify if issue is still valid
believed to be no longer relevant.
Closing ticket as the issue cannot be reproduced.