-
Notifications
You must be signed in to change notification settings - Fork 727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistency between 2.2.0 tag and 2.2.0 binaries and changelog #296
Comments
Thanks, we accidentally missed that when we tagged the release, and corrected the install location in 098b125. (Edit: I noticed you pointed that out already. We'll look into fixing this) |
I've just moved the |
Thanks a lot @saran-t @nimrod-gileadi ! |
Note that I guess now that the only other place that already packaged mujoco, i.e. AUR will need to update their hashes : https://aur.archlinux.org/packages/mujoco . |
I've flagged the package as out of date on AUR. |
Great, thanks! |
Hello everyone, and thanks a lot for open sourcing mujoco!
I am trying to build mujoco 2.2.0 from source. I was expecting it to install the headers in
${CMAKE_INSTALL_PREFIX}/include/mujoco/<...>.h
as this is how headers are arranged in the 2.2.0 binaries, and because the 2.2.0 changelog report, at point 7:However, installing 2.2.0 results in headers installed in
${CMAKE_INSTALL_PREFIX}/include/<...>.h
, and if one checks the source code this is indeed expected, as the line in https://github.com/deepmind/mujoco/blob/2.2.0/CMakeLists.txt#L176 is:instead of
as modified in 098b125 .
Perhaps this is just an artifact of the initial open source release, but I tought it was worth reporting it to as other users may be confused.
As an additional context, I find there were some changes that were ìn
main
but not in2.2.0
that prevented to compile mujoco with gcc on Linux, that you can find at https://github.com/conda-forge/staged-recipes/blob/c6a893a35f34e799522e8be3509a9aa0c1a7bf09/recipes/mujoco/main_backport.patch .The text was updated successfully, but these errors were encountered: