Bring in sync with deepmind/mujoco commit a499b381: #664
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Version 2.1.1: Binaries for ARM64, proper macOS bundles Add Xcode (clang) support with libomp and framework linkage: - Need to put MuJoCo.framework under mujoco_path (eg ~/.mujoco/mujoco210) - Approve the new framework under System Preferences -> Security & Privacy - Install libomp under [/usr/local/lib or /opt/homebrew/lib]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 2.1.1: Binaries for ARM64, proper macOS bundles
Add Xcode (clang) support with libomp and framework linkage:
I have tried to make changes as incremental as possible:
Existence of /usr/bin/gcc-? means gcc is preferred to clang
I think this priority should be reversed under MacOS, but
for now I am just keeping existing behaviour