Automated g4 rollback of changelist 818694877.
*** Reason for rollback *** BEGIN_PUBLIC Holding off on a minor version bump until the next release. *** Original change description *** #mujoco update the version to 3.4.0 ahead of the 3.4.0 release. Bump the version to 3.4.0 ahead of the next release. *** PiperOrigin-RevId: 818748143 Change-Id: I722e9beb80c61a48bd997da6a1840777a81d5036
This commit is contained in:
committed by
Copybara-Service
parent
27e8736fc7
commit
ae1febd83f
@@ -521,7 +521,7 @@ shown in the table below. Their names are in the format ``mjKEY_XXX``. They corr
|
||||
- Maximum number of UI rectangles.
|
||||
Defined in `mjui.h <https://github.com/google-deepmind/mujoco/blob/main/include/mujoco/mjui.h>`_.
|
||||
* - ``mjVERSION_HEADER``
|
||||
- 340
|
||||
- 337
|
||||
- The version of the MuJoCo headers; changes with every release. This is an integer equal to 100x the software
|
||||
version, so 210 corresponds to version 2.1. Defined in mujoco.h. The API function :ref:`mj_version` returns a
|
||||
number with the same meaning but for the compiled library.
|
||||
|
||||
+2
-2
@@ -37,14 +37,14 @@ _____
|
||||
|
||||
The MuJoCo app needs to be run at least once before the native library can be used, in order to register the library as
|
||||
a trusted binary. Then, copy the dynamic library file from
|
||||
``/Applications/MuJoCo.app/Contents/Frameworks/mujoco.framework/Versions/Current/libmujoco.3.4.0.dylib`` (it can be
|
||||
``/Applications/MuJoCo.app/Contents/Frameworks/mujoco.framework/Versions/Current/libmujoco.3.3.7.dylib`` (it can be
|
||||
found by browsing the contents of ``MuJoCo.app``) and rename it as ``mujoco.dylib``.
|
||||
|
||||
Linux
|
||||
_____
|
||||
|
||||
Expand the ``tar.gz`` archive to ``~/.mujoco``. Then copy the dynamic library from
|
||||
``~/.mujoco/mujoco-3.4.0/lib/libmujoco.so.3.4.0`` and rename it as ``libmujoco.so``.
|
||||
``~/.mujoco/mujoco-3.3.7/lib/libmujoco.so.3.3.7`` and rename it as ``libmujoco.so``.
|
||||
|
||||
Windows
|
||||
_______
|
||||
|
||||
Reference in New Issue
Block a user