cmake-init-clang-on-windows
firmware
cmake-init-clang-on-windows | firmware | |
---|---|---|
9 | 1 | |
9 | 12 | |
- | - | |
0.0 | 8.4 | |
over 2 years ago | 8 days ago | |
CMake | C | |
- | Apache License 2.0 |
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.
cmake-init-clang-on-windows
- Using Clang on Windows without Visual Studio.
-
Best compiler for C99
Or LLVM Clang directly without a pseudo *nix environment: https://github.com/friendlyanon/cmake-init-clang-on-windows
-
Cross Compile
While not embedded, but here is an example for compiling with LLVM Clang on Windows without needing vcvarsall.
-
Why does Microsoft want to ditch C?
I was informed that this is not the case. lld supports PE/COFF natively on Windows. You just need to provide some flags to use the MSVC .lib and include files to use Clang properly. Or use the vcvarsall, but that's stinky and I don't like having all that env stuff in my terminal all the time.
-
Quick guide to Windows programming for Unix/Linux C programmers?
Regarding building, I'd advise staying as far away from Mingw, msys and Cygwin as possible. You can just use LLVM Clang without any issue on Windows. You can keep using vim with Clang tools as if you were on Linux still.
-
What Linux distros and environment setup are recommended/optimal for C++ development?
CMake, Clang and Conan work all the same on all operating systems. I don't know why you would like to force yourself into one kind of environment that might not suit your needs in other areas as well. On Windows, you can even use LLVM Clang without godawful hacks like mingw.
-
Build2 seems to have the right idea.
From a quick searching I found what it takes to compile a Windows executable on macOS, these flags could be very easily turned into a toolchain file and the situation would be similar on Linux as well.
-
Thoughts on build systems?
cmake-init was just for a general project setup. One of the examples in fact shows what a toolchain file should look like.
-
Installing c compiler on windows 10.
You can also just use LLVM Clang on Windows. Still requires MSVC installed though, because of link.exe, system .libs and system headers.
firmware
-
Cross Compile
I recently setup a CMake toolchain for STM32 targets here. This might have more features than what you’re looking for but it includes some automatic code generation, multiple projects, and common shared libraries across the projects.
What are some alternatives?
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
qpc - QP/C Real-Time Embedded Framework/RTOS for embedded systems based on active objects (actors) and hierarchical state machines
conan - Conan - The open-source C and C++ package manager
circuits-2022 - Circuit designs for the 2021/2022 vehicle
raylib - A simple and easy-to-use library to enjoy videogames programming
nanopb - Protocol Buffers with small code size
libpq - build2 package for PostgreSQL C client library
sol2 - `build2` package of `sol2`
spdlog - build2 package of the spdlog library
cmkr - Modern build system based on CMake and TOML.
pkgconf - package compiler and linker metadata toolkit
Ease - Ease is a Build System for C++ that strive to acheive simplicity. There is no dependancies, no installation you drop off Ease.hpp in your project and can start writing a build function. The build function will be called and the build will start according to the return value of this function.