Closed mrquincle closed 5 years ago
Almost all (phony) targets have been implemented. It can be optimized a bit, but 90% is done. Depending on the ease of use some more targets might be introduced. For example, we now combine the bootloader-settings with the bootloader. However, when changing the application, the bootloader-settings have to be updated as well. Hence, what to combine with what will be dictated by @vliedel
Latest commit concerning this process: https://github.com/crownstone/bluenet/tree/56a356c0c420d2ad9830d5f64dc7f868724fdb51
Created an up to date INSTALL guide: https://github.com/crownstone/bluenet/blob/master/docs/INSTALL.md
Created an extensive document on the build system: https://github.com/crownstone/bluenet/blob/master/docs/BUILD_SYSTEM.md
A lot of the dependencies are now part of an overarching cmake project. This means tools (like the cross-compiler, the JLink utility, etc.) are automatically downloaded using the two following commands:
What still has to be done is to create additional
cmake
targets, that upload to the remote board, debug remotely, etc.In the
source/CMakeLists.txt
currently, there is a target added which is calledupload
. This callsnrfjprog
under the hood.To call this if you created a
default
target (replace default with your own config):You can also specify another config, for example
boardA
.To build this:
You can use multiple processors, by e.g.
make -j4
.What needs to be done is two things: