Build, Test, and Benchmark
This page describes the public raisim2Lib package workflow. The workspace
downloads RaiSim and rayrai as binary packages, then builds examples and
optional wrappers against those packages. It does not contain the RaiSim engine
source tree. For installation and activation, see Installation. For
repository layout and build output paths, see Project Layout.
Common CMake options
Option |
Meaning |
|---|---|
|
Build C++ examples. Enabled by default. |
|
Build the Python wrapper. |
|
Reserved compatibility option. The current public workspace does not add a MATLAB wrapper subdirectory or build target. |
|
Build documentation through CMake. |
Build examples
Build the package workspace with examples enabled:
cd /path/to/raisim2Lib
cmake -S . -B build-examples \
-DCMAKE_BUILD_TYPE=Release \
-DRAISIM_EXAMPLE=ON
cmake --build build-examples -j12
You can also build only the example CMake project against an installed RaiSim and rayrai package:
cmake -S examples -B /tmp/raisim2lib-examples \
-DCMAKE_BUILD_TYPE=Release \
-DRAISIM_PREFIX=/path/to/raisim \
-DRAYRAI_PREFIX=/path/to/rayrai
cmake --build /tmp/raisim2lib-examples -j12
Run source-built examples from the build directory. They are not installed by
the raisim2Lib install target:
./build-examples/examples/rayrai_tcp_viewer
./build-examples/examples/primitive_grid
/tmp/raisim2lib-examples/rayrai_tcp_viewer
/tmp/raisim2lib-examples/primitive_grid
The release package also includes the prebuilt viewer at
rayrai/bin/rayrai_raisim_tcp_viewer. This is distinct from the
rayrai_tcp_viewer example target, although both provide the same viewer
workflow.
Debug and Release package variants
The current RaiSim package can contain Debug and Release libraries in one
prefix. Its exported targets map a Debug consumer to the Debug library and
Release, RelWithDebInfo, and MinSizeRel consumers to a non-Debug library.
RSDEBUG follows the selected binary automatically. If the prefix contains
only one variant, every consumer configuration maps to that available variant;
building a downstream project in Debug does not manufacture RaiSim debug
assertions when only the Release library is installed.
Timing examples
raisim2Lib includes standalone timing-oriented example executables. The
closed-source engine benchmark runner used for RaiSim release validation is not
shipped in this public binary-package workspace. Run package timing examples on
one thread and repeat the same command several times when comparing package or
scene changes:
cmake --build build-examples \
--target anymal_standing_benchmark articulated_system_benchmark \
granular_media island_sleep_benchmark -j12
OMP_NUM_THREADS=1 OPENBLAS_NUM_THREADS=1 \
./build-examples/examples/anymal_standing_benchmark --fast
OMP_NUM_THREADS=1 OPENBLAS_NUM_THREADS=1 \
./build-examples/examples/articulated_system_benchmark
OMP_NUM_THREADS=1 OPENBLAS_NUM_THREADS=1 \
./build-examples/examples/island_sleep_benchmark --steps=12000
Use Performance for scene-level tuning guidance and for choosing a representative package example before changing solver settings or sensor workloads in a downstream application.
Build the documentation
Prefer the CMake documentation target when you need API reference blocks, because CMake can generate Doxygen XML and pass the Breathe project path to Sphinx:
cmake -S /path/to/raisim2Lib/docs -B /tmp/raisim2lib-docs \
-DRAISIM_DOCS_RAISIM_INCLUDE_DIR=/path/to/raisim2Lib/raisim/include/raisim \
-DRAISIM_DOCS_RAYRAI_INCLUDE_DIR=/path/to/raisim2Lib/rayrai/include/rayrai
cmake --build /tmp/raisim2lib-docs -j12
For prose and link checks, the documentation can also be built directly with Sphinx:
/path/to/raisim2Lib/docs/.venv/bin/sphinx-build \
-b html /path/to/raisim2Lib/docs /tmp/raisim2lib-docs-html
Direct Sphinx builds do not generate Doxygen XML by themselves. They are useful
for quick RST validation, but Breathe API directives will warn unless
breathe_projects.raisim points to generated Doxygen XML.
See Troubleshooting for common warning modes.