[Lldb-commits] [lldb] r179341 - When specifying a relative path for the --framework option to dotest.py, Python would end up being confused and unable to locate the embedded_interpreter module, causing every testcase that uses the Script Interpreter (e.g. functionalities/data-formatter/data-formatter-stl/libstdcpp) to fail without even trying

[Enrico Granata]

Author: enrico
Date: Thu Apr 11 18:40:59 2013
New Revision: 179341

URL: http://llvm.org/viewvc/llvm-project?rev=179341&view=rev
Log:
When specifying a relative path for the --framework option to dotest.py, Python would end up being confused and unable to locate the embedded_interpreter module, causing every testcase that uses the Script Interpreter (e.g. functionalities/data-formatter/data-formatter-stl/libstdcpp) to fail without even trying
This checkin fixes that problem by absolutizing the path before pushing it to the sys.path


Modified:
    lldb/trunk/test/dotest.py

Modified: lldb/trunk/test/dotest.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/test/dotest.py?rev=179341&r1=179340&r2=179341&view=diff
==============================================================================
--- lldb/trunk/test/dotest.py (original)
+++ lldb/trunk/test/dotest.py Thu Apr 11 18:40:59 2013
@@ -913,6 +913,8 @@ def setupSysPath():
     if frameWithVersion != "" :
         lldbPath = before + "LLDB.framework" + after
 
+    lldbPath = os.path.abspath(lldbPath)
+
     # If tests need to find LLDB_FRAMEWORK, now they can do it
     os.environ["LLDB_FRAMEWORK"] = os.path.dirname(os.path.dirname(lldbPath))