stm32-cube-cmake-vscode
samurai
Our great sponsors
| stm32-cube-cmake-vscode | samurai | |
|---|---|---|
| 12 | 10 | |
| 509 | 797 | |
| - | - | |
| 4.9 | 3.2 | |
| 25 days ago | 8 days ago | |
| C | C | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stm32-cube-cmake-vscode
- CI Example on ARM-GCC build with Docker for CMake embedded project.
- Is simplicity studio still garbage?
- Looking for modern CMake tutorials or good open spurce examples
- Packaging for Embedded software
- Migrating from STM32CubeIDE to VisualGDB
- what is your favorite microcontroller platform to develop firmware with and why?
-
How to do STM32 with no abstractions?
Here is a guide to porting an STM32 project from CubeIDE to VSCode and CMake. All credit to MaJerle.
- Can I use STM32codeIDE to write directly in assembly or does it have to be in C only?
-
(FD)CANanalyzer project
Code utilizes STM32Cube ecosystem, VSCode and CMake. Compiler is indeed GCC. Tutorial is here: https://github.com/MaJerle/stm32-cube-cmake-vscode
- Develop STM32 with CubeMX and VSCode
samurai
- Samurai: Ninja-compatible build tool written in C
- Oasis – a small, statically-linked Linux system
-
Ninja is enough build system
Samurai is a faster, drop-in replacement for ninja.
https://github.com/michaelforney/samurai
- samurai: Ninja-compatible build tool written in C
-
Using Landlock to Sandbox GNU Make
"If you want to do what "scrappy Google" did these days, then you should use Python + Ninja."
Or, better yet, use a simpler, faster and more portable^1 Ninja written in C.
https://github.com/michaelforney/samurai
1. The "simpler, faster, and more portable", are the author's claims, not mine. I am not the author.
- samurai: a ninja-compatible build tool written in C.
-
Moving SciPy to the Meson Build System
Why is Python not portable, as in, on which systems is "build Python and then use that to run Meson" not a reasonable option?
The CI for boson seems like it runs on platforms where Python definitely is available, but also I notice the CI uses samurai, a reimplementation of ninja with a similar motivation: https://github.com/michaelforney/samurai
Ninja is in C++ so I am even more confused at Sanurai.
Is this just an implementation-diversity thing? (which is great!)
-
xorg sucks, use swc
This means ninja is popular both on embedded for its tiny footprint (samurai is about 3k sloc and portable), and for humongous projects like Chrome, because it is infinitely scalable in complexity due to its genaration method.
-
Debian Running on Rust Coreutils
You could probably post-process samurai (a rewrite of ninja into C) into a single-file: https://github.com/michaelforney/samurai
What are some alternatives?
libopencm3 - Open source ARM Cortex-M microcontroller library
vivarium - A dynamic tiling Wayland compositor using wlroots
stm32-cmake - CMake for stm32 developing.
Microsoft Research Detours Package - Detours is a software package for monitoring and instrumenting API calls on Windows. It is distributed in source code form.
blue_pill_too - Like the STM32 blue pill there is a STM32F030F4P6 based blue board which so far as I know doesnt have a cool name yet.
build2 - build2 build system
STM32-Dockerfile - STM32 Container for Building with CMake and ARM Toolchain. ST-Link Included.
dwm - LEV Linux's window manager (a fork of dwm)
CMSIS_5 - CMSIS Version 5 Development Repository
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
stlink - Open source STM32 MCU programming toolset
velox - velox window manager