Go to file
Guðni Már Gilbert 745be900ef Run unit tests in parallel if possible
ReadResponse unit tests usually takes at least 30 seconds to run on my
computer, so having the unit tests run on more than one thread makes a
big difference.
2022-10-21 21:30:15 +00:00
.vscode Update vscode to avr-gcc 2022-07-27 17:04:52 +02:00
cmake cmake: Uniform Avr toolchain build with MK3 2022-10-17 17:26:08 +02:00
lib USB cdc stdout stream 2021-10-14 14:27:56 +02:00
src Only set new SGTHRS when planning a Homing move (not regular moves) 2022-10-20 12:09:42 +02:00
tests Run unit tests in parallel if possible 2022-10-21 21:30:15 +00:00
utils Update Jenkins rules to match updated cmake/ninja versions 2022-07-27 17:04:52 +02:00
.clang-format Disable preprocessor code indentation 2021-07-07 16:33:03 +02:00
.cmake-format.py Prepare parts of the build system 2021-04-19 07:03:47 +02:00
.gitignore Prepare parts of the build system 2021-04-19 07:03:47 +02:00
.pre-commit-config.yaml hooks: Update cmake-format to 0.6.13 2022-10-10 11:50:05 +02:00
CMakeLists.txt Revert accidental change 2022-10-20 12:31:12 +02:00
Doxyfile Update doxyfile + document modules namespace 2021-06-30 07:39:31 +02:00
README.md README: Mention the correct output filename 2022-07-27 17:04:52 +02:00
version.cmake Increase version to 2.1.4 2022-10-12 07:45:21 +02:00

README.md

Prusa-Firmware-MMU-Private

How to prepare build env and tools

Run ./utils/bootstrap.py

bootstrap.py will now download all the "missing" dependencies into the .dependencies folder:

  • clang-format-9.0.0-noext
  • cmake-3.22.5
  • ninja-1.10.2
  • avr-gcc-7.3.0

How to build the preliminary project so far:

Now the process is the same as in the Buddy Firmware:

./utils/build.py

builds the firmware.hex in build/mmu_release

In case you'd like to build the project directly via cmake you can use an approach like this:

mkdir build
cd build
cmake .. -G Ninja -DCMAKE_TOOLCHAIN_FILE=../cmake/AvrGcc.cmake
ninja

It will produce a MMU2SR_<version>.hex file.