#bindings #robot #simulator #build #webots

webots-bindings

Webots bindings for Rust

7 releases (breaking)

0.8.0 Jul 4, 2023
0.7.0 Jan 29, 2023
0.6.0 Nov 27, 2022
0.5.0 Sep 27, 2022
0.1.2 Dec 12, 2021

#327 in Simulation


Used in webots

MIT license

10MB
208K SLoC

C++ 160K SLoC // 0.1% comments C 39K SLoC // 0.1% comments JavaScript 3.5K SLoC // 0.0% comments Python 3.5K SLoC // 0.2% comments SWIG 890 SLoC // 0.1% comments Objective-C 821 SLoC Shell 92 SLoC // 0.1% comments Rust 88 SLoC Batch 23 SLoC // 0.1% comments

Contains (DOS exe, 55KB) oversample.exe, (obscure autoconf code, 2KB) webots/src/ode/libccd/configure.ac

Webots controllers in Rust

Status: experimental

This is a reference project that shows how to build controllers for the Webots robot simulator using the Rust programming language.

Getting Started

  1. Download and install Webots for your operating system
  2. Install Rust if you haven't already
  3. Clone this repository recursivly (with submodules)
  4. Run make to compile the Rust controller and copy it into place
  5. Open the sample_project/worlds/my_first_simulation.wbt file in Webots
  6. Run the simulation

You should see "The Rust controller has started" in the Webots console.

To make changes to the controller, you can edit src/main.rs and then run make again. You might need to reset the simulation (File > Reset Simulation) or restart Webots to use the updated code.

How this works

At compile time, I use bindgen to convert a list of Webots C header files (see wrapper.h) into Rust structures and types. Those types form a bridge between the Rust-based controller code and the Webots C library that does the hard work of interacting with the simulation engine. See build.rs and bindings.rs for more details.

Contributing

Improvements are welcome. If you have an idea, please open an issue so that we can discuss it.

TODO

  • Improve API safety. While any of the Webots C functions can be called from Rust, many are marked as unsafe due to raw pointer usage. I have started wrapping a few of them in Rust functions (see lib.rs), but this approach doesn't scale very well given the size of the API.
  • More example controllers
  • Resolve "not FFI-safe" warnings somehow

License

MIT

No runtime deps