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
* Update to Drake 1.42
* Switch to GHCR image with Cirrus secret
* Add noble CI task
* Update LcmDrivenLoop and CassieLcmDrivenLoop to shared_ptr for upstream pybind changes
---------
Co-authored-by: Bibit Bianchini <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+5-14Lines changed: 5 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,9 @@
2
2
Warning! This is very much "development-level" code and is provided as-is. APIs are likely to be unstable and, while we hope for the documentation to be thorough and accurate, we make no guarantees.
3
3
4
4
## Current Continuous Integration Status
5
-
*`master` branch build and unit tests (Ubuntu 18.04): [](https://cirrus-ci.com/github/DAIRLab/dairlib)
6
-
*`master` branch build and unit tests (Ubuntu 20.04): [](https://cirrus-ci.com/github/DAIRLab/dairlib)
7
-
*`master` branch build and unit tests (Ubuntu 20.04 with ROS): [](https://cirrus-ci.com/github/DAIRLab/dairlib)
8
-
* Experimental build against Drake's `master` branch: [](https://cirrus-ci.com/github/DAIRLab/dairlib)
5
+
*`main` branch build and unit tests (Ubuntu Jammy 22.04): [](https://cirrus-ci.com/github/DAIRLab/dairlib)
6
+
*`main` branch build and unit tests (Ubuntu Focal 24.04): [](https://cirrus-ci.com/github/DAIRLab/dairlib)
7
+
* Experimental build against Drake's `master` branch (Jammy): [](https://cirrus-ci.com/github/DAIRLab/dairlib)
9
8
## Complete Build Instructions
10
9
11
10
### Download dairlib
@@ -29,21 +28,13 @@ There is no need to extract the tar.
29
28
The library is meant to be built with Drake (see http://drake.mit.edu/ for more details). There are two ways to use Drake within dairlib:
30
29
31
30
#### Option 1: use pegged revision (Note - These steps may need repeated if switching to a branch with a different pegged revision of drake).
32
-
The only specific action needed here is to install all of Drake's prerequisites. There are two choices for completing this step:
33
31
34
-
a) In `dairlib/install`, run the appropriate `install_prereqs_xxx.sh`. This is untested on mac, and has not been tested to get every dependency for a fresh install.
35
-
36
-
b) Download a source copy of drake, and install pre-requisites as described here: http://drake.mit.edu/from_source.html. Drake dependencies can change without notice. For full compatiability, you may need to checkout the drake commit which is pegged in WORKSPACE to install the correct dependencies. There is no need to build Drake itself. Proceed only until you have run the Drake setup script.
37
-
38
-
bazel will automatically download the pegged revision, specified in the WORKSPACE file. dairlib developers hope to keep this pegged revision current, and ensure that the pegged version will always work with a specific version of dairlib.
32
+
In `dairlib/install`, run the `install_prereqs_ubuntu.sh`. Our build process does not currently support MacOS, though it has in the past and likely will in the future.
39
33
40
34
This option is recommended for users who are not currently editing any source code in Drake itself.
41
35
42
36
#### Option 2: source install of Drake
43
-
Complete both steps (a) and (b) above. By running the drake install script after the dairlib install script, you are capturing any dependency changes between the pegged revision and the current Drake master, while still getting any aditional dairlib dependencies we may add. There is no need to build Drake. Next, to tell dairlib to use your local install, set the environment variable `DAIRLIB_LOCAL_DRAKE_PATH`, e.g.
If you would like to use your own local install of Drake, likely because you are modifying it, when you build with Bazel you will need to use `bazel build --override_module=drake=/home/user/my-workspace/drake <package you are building>` (using the appropriate directory for your own install). There is no need to build Drake.
47
38
48
39
### IDE setup
49
40
JetBrains IDEs have worked well for us and are available for free to students. For C++ development using the CLion Bazel plugin, see https://drake.mit.edu/clion.html and replace `drake` with `dairlib` in the "Setting up Drake in CLion" section.
0 commit comments