Skip to content

Conversation

@Shivam-Bhardwaj
Copy link

Summary

Improves the build-from-source documentation for Python bindings to address common user questions.

Closes #1708

Changes

  • Add tip explaining which steps to repeat when modifying C/C++ code
  • Clarify step 3 with two clear options (download prebuilt vs build from source)
  • Use export for environment variables for better shell compatibility
  • Explain why MUJOCO_PLUGIN_PATH is required even without plugins
  • Add concrete examples for Linux and macOS configurations

Motivation

Users building from source were confused about:

  1. Which steps to repeat after modifying C code
  2. Whether building MuJoCo itself was required
  3. How to properly set environment variables
  4. Why MUJOCO_PLUGIN_PATH was needed

- Add tip explaining which steps to repeat when modifying C/C++ code
- Clarify step 3 with two clear options (download vs build from source)
- Use `export` for environment variables for clarity
- Explain why MUJOCO_PLUGIN_PATH is required
- Add concrete examples for Linux and macOS

Closes google-deepmind#1708
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build from Source incl. Python Bindings

1 participant