Skip to content

Conversation

@anchapin
Copy link
Collaborator

@anchapin anchapin commented Jan 5, 2026

Enhance the CMake build configuration for macOS by adding the macOS version specification and updating the installation RPATH to include the library path. This ensures better compatibility and functionality for macOS bundles.

@anchapin anchapin added the Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge. label Jan 5, 2026
@anchapin anchapin self-assigned this Jan 5, 2026
@github-actions
Copy link

github-actions bot commented Jan 6, 2026

🧪 Test Results Dashboard

Summary

Metric Value
Total Tests 4150
Passed 4150
Failed 0
Errors 0
Skipped 0
Success Rate 100.0%
Generated 2026-01-06 19:19:02 UTC

✅ All Tests Passed!

📊 Test Run Information

Run XML File Status
run1 results.xml ✅ Found
run3 results.xml ✅ Found
run2 results.xml ✅ Found

@ci-commercialbuildings
Copy link
Collaborator

ci-commercialbuildings commented Jan 6, 2026

@anchapin anchapin merged commit 7eb683b into develop Jan 6, 2026
7 checks passed
@anchapin anchapin deleted the mac-fixes branch January 6, 2026 21:46
-DBUILD_PYTHON_BINDINGS:BOOL=ON \
-DBUILD_PYTHON_PIP_PACKAGE:BOOL=OFF \
-DCMAKE_INSTALL_RPATH="@loader_path;@executable_path" \
-DCMAKE_INSTALL_RPATH="@loader_path;@executable_path;@loader_path/../lib" \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this for #5574 ?

This is the wrong solution IMHO. This should be done in cmakelists, not via a command line parameter (which anyone building is likely to forget to add).

Copy link
Collaborator

@jmarrec jmarrec Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could be that #5574 exists is because you are passing this variable CMAKE_INSTALL_RPATH to begin with (or something similar). In any case I don't think we want to do that.

We never explicitly added libopenstudiolib.dylib into the openstudio.bundle and it has always worked fine, until the full-build workflow was added.

$ otool -L /Applications/OpenStudio-3.10.0/Ruby/openstudio.bundle
/Applications/OpenStudio-3.10.0/Ruby/openstudio.bundle:
	/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 61439.101.1)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 3423.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1900.178.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1351.0.0)
$ otool -L /Applications/OpenStudio-3.11.0-rc2/Ruby/openstudio.bundle
/Applications/OpenStudio-3.11.0-rc2/Ruby/openstudio.bundle:
	@rpath/libopenstudiolib.dylib (compatibility version 0.0.0, current version 0.0.0)
	/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 61439.120.27)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 3502.1.255)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1900.180.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1351.0.0)

Should track where this started popping.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get why passing CMAKE_INSTALL_RPATH, seems to be stemming from 40d0625 and the commit message doesn't explain anything

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that you made a PR #5583 to fix this so that CMAKE_INSTALL_RPATH is no longer provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants