I've just released the #Python wheels for today's release of #CMake 4.0! https://pypi.org/project/cmake/ Remember to set your CMake minimum version to at least 3.5 (3.15 or better preferred) and set a maximum version too (newer CMake follows the policies of the maximum version) #release
Boost Your CMake Development with Copilot Custom Instructions.
Boost Your CMake Development with Copilot Custom Instructions.
buff.ly/Fl5FlsB
#cpp #ai #cmake #visualstudio #copilot #githubcopilot #productivity
Boost Your CMake Development w...
iRODS Development Update: March 2025
https://irods.org/2025/03/irods-development-update-march-2025/
Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!
On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 
Part 2 of my Intro to #Zephyr series is out! CMake is a popular tool, even among embedded developers, and Zephyr relies heavily on it for its build process. Get a quick primer on #cmake and see how Zephyr uses it!
https://youtu.be/HSWazjB63cU
Packaging a C++ library with CMake when multi-configuration generator is used is so frustrating, if not borderline impossible...
The closest I've got so far is to build two archives (debug and release) and somehow merge them into one...
Whohoo! Managed to fix cmake so I would be able to bump version for Qt-Creator!
Patch for cmake (+ version bump to 3.31.5) coming up shortly. If upstream is open for the PR this should make a good candidate for Haiku.
cmake 3.31.5, Qt-Creator 15.0.1, Qt 6.8.2
#HaikuOS #cmake #Qt #development #IDE
EDIT: patch merged upstream 
Mini-rant ahead:
I'm delving into #cmake to try to make it build a compile_commands.json file to work with #retrocomputing C header files, specifically the #Psion SIBO C SDK (from the early 90s).
I don't actually want cmake to do anything but tell clangd what to do, so that I've got a working language server in NeoVim.
I don't need it to build any Makefiles, I don't need it to tell a compiler what to do. I just want clangd to treat my old 16-bit real mode code correctly, and that the header files are in ~/dosbox/sibo-c/SIBOSDK/include/.
Note that I can't point it at the compiler, because the compiler (TopSpeed) runs in DOSBox. There is no modern compiler that will work.
So... Do I have to fake it somehow? For example, do I have to tell cmake that it's actually using a different compiler (e.g. #Watcom) to make it behave correctly?
New on the blog: Discover how we used #Nix and #NixOS to package a hybrid #CMake project with #Rust dependencies using Corrosion! Learn how to tackle dependency management challenges and build #reproducible systems. 
Read here: https://cyberus-technology.de/en/articles/nix-cmake-corrosion #DevOps #FOSS
I've been experimenting with emscripten lately, so I created a skeleton cmake project that prepares emsdk and use it to compile C code instead of using a C compiler #cmake #emscripten #webassembly https://github.com/pvmm/skeleton-emsdk-cmake
I've been fighting with #Fedora40, #cmake, and #qt5 all day, and am at my wits end.
cmake needs to know the location of the qt5-config.cmake file, but from what I've been able to tell, there is no such file on my computer.
There are several QT5 directories in /usr, but all are completely empty. I'm not even sure if QT5 is actually installed at this point. (Though the packages qt5-qtbase and qt5-qtsvg definitely are.)
The #github repository of my #sega #mastersystem and #gamegear #emulator called "Masterlator" is now public 
I've rewritten the code in proper C++, use #cmake as the build system, utilize #sdl2 and added a new #debugger with #wladx compatible *.sym file support, memory viewer and tile/sprite viewer. It's rather basic now but will hopefully be a good tool for #homebrew game #development in the future.
