verified to work on real robots adds sim eclipse plugins, fixed JavaGazebo, made wpilibC++Sim build on windows - Java and C++ simulation robot programs run on windows - simulation eclipse plugin delivers models and gazebo plugins - Java Gazebo now respects GAZEBO_IP variables and can work across networks - hal and network tables win32 hacked to work on windows - smart dashboard broken on windows due to network tables hacks - wpilibC++Sim, gz_msgs, and frcsim_gazebo_plugins build with CMake - removed constexpr for cross platform compatibility - msgs generated using .protos as a part of build process - some spare and unused cmake/pom files deleted - simulation ubuntu debians removed entirely - refactored CMake project flags and macros - updated to match non-sim C++ API - fixed and updated documentation - servo added to simulation Change-Id: Ia702ff0f1fee10d77f543810ad88f56696443b05
1.5 KiB
Building everything requires Maven, and the arm jdk
To build eclipse plugins (also build wpilibc/j)
./gradlew eclipsePlugins //this is what is most often used
other possible targets are "build" or "frcuserprogram"
To build on CMake Projects (gz_msgs, frc_gazebo_plugins, WPILIbC++Sim
//STARTING FROM ALLWPILIB DIRECTORY
$> mkdir build
$> cd build
// on linux
$> cmake .. && make -j4
// on windows
$> ..\configure.bat
$> jom
You can build subprojects of CMake stuff
To find all of them, you can navigate to "build" and type "make " Examples: make WPILibC++Sim make dc_motor make gz_msgs make clean
Note: For the latest version of FRCSim that uses the NI Driverstation, there is a circular dependency between CMake and Gradle projects.
wpilibc++sim depends on hal which is gradle, but eclipse plugins depends on wpilibc++sim which is cmake so if you want everything to work nicely, run: ./gradlew :hal:build mkdir build; cd build //if you haven't already done so cmake .. && make -j4 ./gradlew eclipsePlugins //or whatever else
Other gradle options
./gradlew tasks //list some available tasks
TODO: Explain maven.... TODO: how to import into eclipse correctly...
GCC versions
Update arm-toolchain.cmake if the triplet changes (eg using Ubuntu repo arm compiler is arm-linux-gnueabi) or in a non-standard location. Currently it assumes that the compiler is on the path.