Instead of assuming that SWIG generated files (e.g. lldb.py) will live
in scripts, we should set it to $LLDB_PYTHON_TARGET_DIR. This variable is set to
scripts, except when building LLDB.framework when it is set to
LLDB_FRAMEWORK_DIR.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
I'm not sure who else would be interested in reviewing this. If you know somebody, please add them. :)
scripts/CMakeLists.txt | ||
---|---|---|
38 ↗ | (On Diff #149843) | Yes. Those paths were actually the same if you were not building the framework, which is why this bug never surfaced. Specifically, ${CMAKE_CURRENT_BINARY_DIR} in scripts/CMakeLists.txt resolves to the same path as ${CMAKE_CURRENT_BINARY_DIR}/scripts in the top level CMakeLists.txt. The pitfall is the assumption that this path is always the same as ${LLDB_PYTHON_TARGET_DIR}, which it is not if you are trying to build the framework. |
scripts/CMakeLists.txt | ||
---|---|---|
38 ↗ | (On Diff #149843) | Makes sense. This should be good to go then. |