| 1 | | The daily build has an RPATH in the framework Python library |
| 2 | | |
| 3 | | $ otool -l /Applications/ChimeraX.app/Contents/Library/Frameworks/Python.framework/Versions/3.5/Python |
| 4 | | ... |
| 5 | | Load command 12 |
| 6 | | cmd LC_RPATH |
| 7 | | cmdsize 72 |
| 8 | | path /private/var/tmp/chimerax_build/develop/chimerax/build/lib (offset 12) |
| 9 | | |
| 10 | | The ChimeraX executable has the correct RPATH: |
| 11 | | |
| 12 | | $ otool -l /Applications/ChimeraX.app/Contents/MacOS/ChimeraX |
| 13 | | ... |
| 14 | | Load command 15 |
| 15 | | cmd LC_RPATH |
| 16 | | cmdsize 40 |
| 17 | | path @executable_path/../lib (offset 12) |
| 18 | | |
| 19 | | |
| 20 | | The Mac install_name_tool command can change or delete the RPATH in the Python framework library. If we want to be able to run the Chimera Python without running the Chimera app we may want to give it a correct RPATH for finding the Python framework libraries. If instead we delete the RPATH then the standalone Python in the app may not start. |
| | 1 | Reassigning to Greg to add Makefile command to fix Python framework RPATH. |