You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm an engineer and I'm trying to use MuJoCo for a multibody simulation.
I was trying to understand the workings of Mujoco better and investigate some bugs that occurred for me. I've built the project including python bindings from source.
My question is, which buil step do I need to repeat, such that changes in the c-code (e.g., src/xml/xml_api.cc) influence the python built?
Also, the path definition should have an additional keyword export to make the variables to environment variables, right?
And why is the variable MUJOCO_PLUGIN_PATH needed? Does it not directly follow from the main repository? Or did I not understand that variable correctly?
The text was updated successfully, but these errors were encountered:
Hi,
I'm an engineer and I'm trying to use MuJoCo for a multibody simulation.
I was trying to understand the workings of Mujoco better and investigate some bugs that occurred for me. I've built the project including python bindings from source.
My question is, which buil step do I need to repeat, such that changes in the c-code (e.g.,
src/xml/xml_api.cc
) influence the python built?And a comment, in the python source build instruction, it would be useful to additionally add, that the general mujoco build needs to be executed, or did I miss something? => After 3. one has to follow the instructions on https://mujoco.readthedocs.io/en/latest/programming/#building-mujoco-from-source right?
Also, the path definition should have an additional keyword
export
to make the variables to environment variables, right?And why is the variable MUJOCO_PLUGIN_PATH needed? Does it not directly follow from the main repository? Or did I not understand that variable correctly?
The text was updated successfully, but these errors were encountered: