The following guide will help you setup the development environment for embedded development with the Zeropilot. If youryou'e re just joining our team, only do the steps marked "mandatory". All "optional" may become mandatory for you in the future, depending on what sort of tasks youryou'e re picking up.
First things first (all steps mandatory)
To develop anything at all, youryou'e re going to need a text editor, command line access, and cmake.
...
What text editor you use is entirely up to you. Anything from vim to visual studio is fine. If you don't have a preffered preferred one yet, I'd suggest sublime text or visual studio code as quite a few of our members use those.
...
To make sure Cmake is properly installed, open the command line and type "cmake". If the cmake help menu comes up, your'e you’re good to go.
Building the code (some steps mandatory)
...
Because writing unit tests is madatorymandatory, stting setting up this toolchain is also mandatory and instructions for doing that can be found here.
...
The team leverages simulation to ensure that the entirety of the autopilot firmware is capable of flying the airplane the way we want it to fly. Depending on what your'e you’re developing though, setting up the simulation stuff is optional. The simulations run locally, on each of our computers, and so they share some the unit testing toolchain. However, setting up the simulation requires a few more steps which can be found here.
...