docs.rs failed to build safe-vex-3.2.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
safe-vex-4.4.0
safe-vex
A safe, reliable and comprehensive wrapper around the vex-rt library that will never panic!
Disclamer
safe-vex is an open-source community project. safe-vex is neither endorsed by or affiliated with Innovation First, Inc. VEX and VEX Robotics are trademarks or service marks of Innovation First, Inc. safe-vex is also not developed by the same developers at vex-rt rather it is an independant project.
Quickstart (Natively)
you will need:
- A rust toolchain managed by
rustup: - An
arm-none-eabitoolchain gccandlibclang-dev/libclang- (optional)
libc6-devif rustc is throwing the error:
/usr/lib/arm-none-eabi/include/sys/reent.h:14:10: fatal error: 'stddef.h' file not found
thread 'main' panicked at /home/dev/.cargo/registry/src/index.crates.io-6f17d22bba15001f/vex-rt-0.15.1/build/main.rs:266:10:
Could not generate bindings.: ClangDiagnostic("/usr/lib/arm-none-eabi/include/sys/reent.h:14:10: fatal error: 'stddef.h' file not found\n")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
- The
pros-cliinstalled throughpip
then:
- Clone the
safe-vexproject template by running the following command:
- Enter the newly cloned directory
- Turn on and connect to the vex v5 brain
- Give permission to upload code to the robot with: (doesn't matter if this fails)
||
- While connected to the v5 brain run:
- Your robot should now be up and running :D
Quickstart (with Docker)
you will need:
docker
then:
- Clone the
safe-vexproject template by running the following command:
- Enter the newly cloned directory
- Build the docker image with:
- Turn on and connect to the vex v5 brain
- Give permission to upload code to the robot with: (doesn't matter if this fails)
||
- Run the docker container interactively with:
- Run
cargo run --releasein the docker container while connected to the v5 brain - Your robot should now be up and running :D