Why tup is used instead of CMake for compiling the firmware?

Hi, I am curious why tup is used instead of CMake for compiling the ODrive firmware?. Is there any specific reason for this ?.

Not really. Quick and easy to setup, handles the dependencies well. None of us had CMake experience when we started to use it, and it works so no real reason to change after :stuck_out_tongue:

1 Like

Alright. I have prior experience with CMake but not tup, when I am trying to setup tup on Apple M1 to compile the ODrive firmware it gets a bit messier and breaks the dependencies of arm64 and x86 and some of the dependency libraries were not yet fully ported on to arm64.:D. May be I will figure out someway to compile firmware with CMake:D.

Well, you can try to compile tup for M1 lol GitHub - gittup/tup: Tup is a file-based build system.