I'm thinking a "GUI" would help, that could perhaps be done say using a 'web based' setup It skipped over huge swatches of ifdefs and just build what is needed. I think it is partly because cmake narrows the build to a particular variant/board and possibly even a particular series. I'd guess it is sufficiently unique for now. It seemed the '2 level' (or in fact 3 level) series - board namespace is simplified to a single list? That would help with the -b board parameter in case of a mismatch. That's 'ok' as after all a variant is a 'library'Ī thing though would cmake/scripts/cmake_easy_setup.py ![]() It is also rather interesting that I noted in each variant directory, e.g. I'd guess it would be merged in the main wiki in its own section when the commits are merged. Would be good to document the generation steps say after adding a custom board. It seemed the boards db file is generated? it is huge I just tried it out (in linux), really cool This would also make sense regarding debuggers.Īnyway this topic will definitely get discussed on my end I'll let you know what comes out of it. I am also working on the integration with IDEs, maybe this is something that can be delegated to them? Considering for example ST's Cube IDE, or Cube2. Regarding the bootloader support: I shall consider integrating this feature, but some of the changes it carries may not be CMake-friendly (e.g., selecting the Serial port the board is on.). 60% build time using CMake vs arduino-cli on my machine !) I would add that CMake is much faster at building than Arduino IDE, at least under Windows. I see we have the same view on the benefits of CMake vs Arduino IDE. ![]() The thing is the CMake files are configurations and macros which makes this more feasible.Īnd it allows 'swapping' of libraries, e.g. flash utilities) can possibly be added along the way.ĬMake adds more flexibility than do the classical 'arduino ide'. Automatic library dependency detection (you have to state explicitly that you use, e.g., the Wire library) ģrd party bootloaders and utilities (e.g.Library management (download, update.).Third-party bootloaders (Maple DFU Bootloader, HID Bootloader 2.2).Third-party Arduino libraries (typically in ~/Arduino/sketchbook).Reading board definitions from boards.txt.All the feature switches present in the Arduino IDE (and more!).Building a sketch for any board the STM32 core supports, _quickly_ (about 10s on my machine).The setup instructions are listed on a dedicated wiki page briefly, you'll need CMake, Ninja, Python, plus a few Python modules to get running. Here are the various entry points to get you started:Īlthough being comfortable with CMake would be useful when using this project, it is not really a requirement: I have done my best to abstract any CMake-related complexity away. I have been told this was a feature some of you had requested, to overcome limitations of Arduino IDE (e.g., long build time.).Īs this project is coming into beta, I would really like to get some feedback on it, in terms of features, performance, usability. ![]() As I said in my introduction message, I am currently working on the CMake support for STM32 boards.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |