People will complain about CMake and then have a 5 minutes autotools configure step that checks whether your compiler can include <stdio.h> and if sizeof char is 1 by running serial bash executions with a new process each time.
November 8, 2026 at 12:26 PM
People will complain about CMake and then have a 5 minutes autotools configure step that checks whether your compiler can include <stdio.h> and if sizeof char is 1 by running serial bash executions with a new process each time.
Lol, there are like 6 GPU languages and a CMake like IR that can transpile into any of them.
November 9, 2026 at 6:34 PM
Lol, there are like 6 GPU languages and a CMake like IR that can transpile into any of them.
It's bad. we all know this site's slopped up, but even Linus Torvalds is apparently all-in on this, stuff like git and the Linux kernel is tainted, to say nothing of everything from mpv, VLC, LibreOffice, all major web browsers, cmake even fucking ffmpeg
we are turbo-fucked
we are turbo-fucked
November 7, 2026 at 6:40 AM
It's bad. we all know this site's slopped up, but even Linus Torvalds is apparently all-in on this, stuff like git and the Linux kernel is tainted, to say nothing of everything from mpv, VLC, LibreOffice, all major web browsers, cmake even fucking ffmpeg
we are turbo-fucked
we are turbo-fucked
vibe coding the “business logic” is called running your business on vibes
But nothing is lost by me not needing to fuck with CMake ever again
But nothing is lost by me not needing to fuck with CMake ever again
November 5, 2026 at 7:56 PM
vibe coding the “business logic” is called running your business on vibes
But nothing is lost by me not needing to fuck with CMake ever again
But nothing is lost by me not needing to fuck with CMake ever again
no; but the pico sdk is heavily cmake based, so if you can set-up a cmake project youre probably golden. (debugger is another story, i guess)
November 5, 2026 at 7:38 AM
no; but the pico sdk is heavily cmake based, so if you can set-up a cmake project youre probably golden. (debugger is another story, i guess)
Monte Carlo Simulator
This project is build using C++ and CMake as its build system. My main goal with this project is to gain experience with C++ and also learn CMake. This project basically predicts possible future…
This project is build using C++ and CMake as its build system. My main goal with this project is to gain experience with C++ and also learn CMake. This project basically predicts possible future…
Monte Carlo Simulator
This project is build using C++ and CMake as its build system. My main goal with this project is to gain experience with C++ and also learn CMake. This project basically predicts possible future…
news-area.com
November 8, 2026 at 6:57 PM
Monte Carlo Simulator
This project is build using C++ and CMake as its build system. My main goal with this project is to gain experience with C++ and also learn CMake. This project basically predicts possible future…
This project is build using C++ and CMake as its build system. My main goal with this project is to gain experience with C++ and also learn CMake. This project basically predicts possible future…
Other improvements:
• Safer async callback shutdown
• Message (16 MiB) & handshake (16 KiB) size limits
• WebSocket frame validation & IPv6 handling
• Updated Boost.Asio / standalone Asio support
• CMake integration, tests & CI
#cplusplus #opensource
• Safer async callback shutdown
• Message (16 MiB) & handshake (16 KiB) size limits
• WebSocket frame validation & IPv6 handling
• Updated Boost.Asio / standalone Asio support
• CMake integration, tests & CI
#cplusplus #opensource
November 6, 2026 at 1:42 PM
Other improvements:
• Safer async callback shutdown
• Message (16 MiB) & handshake (16 KiB) size limits
• WebSocket frame validation & IPv6 handling
• Updated Boost.Asio / standalone Asio support
• CMake integration, tests & CI
#cplusplus #opensource
• Safer async callback shutdown
• Message (16 MiB) & handshake (16 KiB) size limits
• WebSocket frame validation & IPv6 handling
• Updated Boost.Asio / standalone Asio support
• CMake integration, tests & CI
#cplusplus #opensource
#gentoo #python #symengine #findcython #patch
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -37,6 +37,8 @@
set(CYTHON_MIN "3.1")
endif()
+list(APPEND CMAKE_MODULE_PATH "/usr/share/cmake/Modules")
+
find_package(Cython ${CYTHON_MIN} MODULE REQUIRED) […]
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -37,6 +37,8 @@
set(CYTHON_MIN "3.1")
endif()
+list(APPEND CMAKE_MODULE_PATH "/usr/share/cmake/Modules")
+
find_package(Cython ${CYTHON_MIN} MODULE REQUIRED) […]
Original post on misskey.io
misskey.io
November 8, 2026 at 9:58 AM
#gentoo #python #symengine #findcython #patch
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -37,6 +37,8 @@
set(CYTHON_MIN "3.1")
endif()
+list(APPEND CMAKE_MODULE_PATH "/usr/share/cmake/Modules")
+
find_package(Cython ${CYTHON_MIN} MODULE REQUIRED) […]
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -37,6 +37,8 @@
set(CYTHON_MIN "3.1")
endif()
+list(APPEND CMAKE_MODULE_PATH "/usr/share/cmake/Modules")
+
find_package(Cython ${CYTHON_MIN} MODULE REQUIRED) […]
A reminder to everyone that _ITERATOR_DEBUG_LEVEL=2 is on in _everything_ on Windows. CMake, VS projects, vckpg, anything that sets /DEBUG and doesn't override the define.
And it's ABI breaking to turn it off, so your whole toolchain and package tree needs the toggle.
And it's ABI breaking to turn it off, so your whole toolchain and package tree needs the toggle.
November 8, 2026 at 3:03 PM
A reminder to everyone that _ITERATOR_DEBUG_LEVEL=2 is on in _everything_ on Windows. CMake, VS projects, vckpg, anything that sets /DEBUG and doesn't override the define.
And it's ABI breaking to turn it off, so your whole toolchain and package tree needs the toggle.
And it's ABI breaking to turn it off, so your whole toolchain and package tree needs the toggle.
What do you use to combine VS and CMake? I just use CMake-Gui.exe
November 5, 2026 at 10:04 AM
What do you use to combine VS and CMake? I just use CMake-Gui.exe
Yeah, I can understand complaints about CMake but if your proposed replacement even hints about autotools I’ve already lost respect for your technical competence as it relates to build systems. Leave it in the 80s where it belongs, if you don’t like CMake use Meson or something.
November 8, 2026 at 3:49 PM
Yeah, I can understand complaints about CMake but if your proposed replacement even hints about autotools I’ve already lost respect for your technical competence as it relates to build systems. Leave it in the 80s where it belongs, if you don’t like CMake use Meson or something.
Earlier today I discovered that the command line argument that causes CMake with the MSVC generator to build a 64-bit build will 100% of the time result in an unrecoverable error on the Ninja build, meaning there is no way to imagine a single invocation which runs on both MSVC and Ninja systems
November 7, 2026 at 10:50 PM
Earlier today I discovered that the command line argument that causes CMake with the MSVC generator to build a 64-bit build will 100% of the time result in an unrecoverable error on the Ninja build, meaning there is no way to imagine a single invocation which runs on both MSVC and Ninja systems
CMake is not great but unfortunately every single other alternative is worse.
We used to have our own build system written in Perl that was twice as fast as CMake but it had a bus factor of less than 1 and would fall apart requiring days of debugging if you tried to change literally any part of it.
We used to have our own build system written in Perl that was twice as fast as CMake but it had a bus factor of less than 1 and would fall apart requiring days of debugging if you tried to change literally any part of it.
November 9, 2026 at 9:57 AM
CMake is not great but unfortunately every single other alternative is worse.
We used to have our own build system written in Perl that was twice as fast as CMake but it had a bus factor of less than 1 and would fall apart requiring days of debugging if you tried to change literally any part of it.
We used to have our own build system written in Perl that was twice as fast as CMake but it had a bus factor of less than 1 and would fall apart requiring days of debugging if you tried to change literally any part of it.
lumis_wasm_cmake 0.26.8 [updated]
Tree-sitter parser and queries for cmake, compiled to WASM for Lumis
Licenses: MIT
Tree-sitter parser and queries for cmake, compiled to WASM for Lumis
Licenses: MIT
November 7, 2026 at 2:15 PM
lumis_wasm_cmake 0.26.8 [updated]
Tree-sitter parser and queries for cmake, compiled to WASM for Lumis
Licenses: MIT
Tree-sitter parser and queries for cmake, compiled to WASM for Lumis
Licenses: MIT
New release: zlib was tagged with v1.4.
zlib v1.4
# zlib 1.4 Release Notes
_November 4, 2026_
## **Changes in 1.4 (since 1.3.2)**
### Breaking changes
- **CMake:**
- The minimum CMake version is...
github.com
November 5, 2026 at 6:03 PM
New release: zlib was tagged with v1.4.
A wild Cmake appears
November 2, 2026 at 5:16 PM
A wild Cmake appears
I've been using meson a bunch more for personal projects, and tbh it's quite a nice reprieve from CMake
there are quite a few kinks that I'd really like to see ironed out though
there are quite a few kinks that I'd really like to see ironed out though
November 8, 2026 at 8:52 AM
I've been using meson a bunch more for personal projects, and tbh it's quite a nice reprieve from CMake
there are quite a few kinks that I'd really like to see ironed out though
there are quite a few kinks that I'd really like to see ironed out though
I’m looking at you, g-ddamned gnu configure, and you, all the fucking bespoke make makers that come with chrome and firefox, and particularly you cmake!
November 6, 2026 at 8:25 PM
I’m looking at you, g-ddamned gnu configure, and you, all the fucking bespoke make makers that come with chrome and firefox, and particularly you cmake!
i used to fuckin' hate cmake but we get along now
November 4, 2026 at 9:32 PM
i used to fuckin' hate cmake but we get along now
kinda want to write a linker, but that's going to require me to write linker scripts and i am just not feeling it to deal with making CMake play ball with _two_ bison parsers rn
November 6, 2026 at 8:47 PM
kinda want to write a linker, but that's going to require me to write linker scripts and i am just not feeling it to deal with making CMake play ball with _two_ bison parsers rn
How do you specify an alternate compiler with Cmake + VS? Mine still keeps trying to use the VS cl.exe and linker.
November 5, 2026 at 8:49 AM
How do you specify an alternate compiler with Cmake + VS? Mine still keeps trying to use the VS cl.exe and linker.
Experimented with using zig build as a replacement for cmake last night.
After some fanjangling I have a little build script for a c99 project that builds a static+dyn lib & app
It’s a nice build system, I’m a fan of the .zon files to store lists of stuff, it makes the build script very concise.
After some fanjangling I have a little build script for a c99 project that builds a static+dyn lib & app
It’s a nice build system, I’m a fan of the .zon files to store lists of stuff, it makes the build script very concise.
November 6, 2026 at 8:37 AM
Experimented with using zig build as a replacement for cmake last night.
After some fanjangling I have a little build script for a c99 project that builds a static+dyn lib & app
It’s a nice build system, I’m a fan of the .zon files to store lists of stuff, it makes the build script very concise.
After some fanjangling I have a little build script for a c99 project that builds a static+dyn lib & app
It’s a nice build system, I’m a fan of the .zon files to store lists of stuff, it makes the build script very concise.
Well I have a parallel version of my home engine using zig build & zigCC.
I can confirm that it’s much faster at resolving the work before kicking off a compile&link
Previously just a single .c file it would take around 3.5s w/ 85% being cmake/ninja.
Zigbild debug this is ~50ms + compile/link
I can confirm that it’s much faster at resolving the work before kicking off a compile&link
Previously just a single .c file it would take around 3.5s w/ 85% being cmake/ninja.
Zigbild debug this is ~50ms + compile/link
November 8, 2026 at 2:08 PM
Well I have a parallel version of my home engine using zig build & zigCC.
I can confirm that it’s much faster at resolving the work before kicking off a compile&link
Previously just a single .c file it would take around 3.5s w/ 85% being cmake/ninja.
Zigbild debug this is ~50ms + compile/link
I can confirm that it’s much faster at resolving the work before kicking off a compile&link
Previously just a single .c file it would take around 3.5s w/ 85% being cmake/ninja.
Zigbild debug this is ~50ms + compile/link
