Mastodon

HaraldMost build systems have their own syntax to write build scripts with the twist that functions are only run if their output could differ from the last call.I turned this upside-down thing on its feet again, providing a Python library to run functions only if needed.So your build script is just a Python script, but still does not run functions unnecessarily.<a href="https://codeberg.org/harald/pythonbuilder" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/harald/pythonbuilder</a><a href="https://nrw.social/tags/pythonbuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#pythonbuilder</a> <a href="https://nrw.social/tags/buildtool" class="mention hashtag" rel="nofollow noopener" target="_blank">#buildtool</a> <a href="https://nrw.social/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a> <a href="https://nrw.social/tags/gradle" class="mention hashtag" rel="nofollow noopener" target="_blank">#gradle</a> <a href="https://nrw.social/tags/ant" class="mention hashtag" rel="nofollow noopener" target="_blank">#ant</a> <a href="https://nrw.social/tags/buildautomation" class="mention hashtag" rel="nofollow noopener" target="_blank">#buildautomation</a>

Jan :rust: :ferris:Unhinged (Software Dev)

Jan :rust: :ferris:Ok, I have to correct myself:Compiling any C/C++ project on Windows is an absolute clusterfuck!I've now almost spent more time trying to compile my program for Windows than writing the actual code for it - let that sink in!<a href="https://floss.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://floss.social/tags/CPlusPlus" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPlusPlus</a> <a href="https://floss.social/tags/Compile" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compile</a> <a href="https://floss.social/tags/Build" class="mention hashtag" rel="nofollow noopener" target="_blank">#Build</a> <a href="https://floss.social/tags/BuildSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#BuildSystem</a> <a href="https://floss.social/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a>

Jakub NerudaOne of the things a good CMake-powered C++ library should do is to test its own integration - in other words, if others can plug it into their projects. One reason is obvious - nobody will use your library if they can't. The second one is pragmatic - the tests act as documentation for the users.I've spent many hours refining my integration testing of CMake code, and I've compiled my learnings into the following article: ➤ <a href="https://medium.com/@nerudaj/cmake-integration-testing-4d71184525ea" rel="nofollow noopener" translate="no" target="_blank">https://medium.com/@nerudaj/cmake-integration-testing-4d71184525ea</a>I've also fallen into the inevitable rabbit hole of dependency management in CMake, so if you want to learn about that, the article has you covered as well! 😵‍💫What do you think? Are there other aspects of integration that are worth testing? And would you be interested in an article on how to make findable prebuilt packages with CMake?<a href="https://techhub.social/tags/cpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#cpp</a> <a href="https://techhub.social/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a> <a href="https://techhub.social/tags/integrationtesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#integrationtesting</a>

RainTechnology/Programs that are (still) black magic to me and I will never understand how to properly use them no matter how bad i want to. (In no special order) - <a href="https://melonbread.xyz/tags/Blender" rel="nofollow noopener" target="_blank">#Blender</a> (3D Modeling in general) - <a href="https://melonbread.xyz/tags/CMake" rel="nofollow noopener" target="_blank">#CMake</a> - <a href="https://melonbread.xyz/tags/SELinux" rel="nofollow noopener" target="_blank">#SELinux</a> - <a href="https://melonbread.xyz/tags/freeCAD" rel="nofollow noopener" target="_blank">#freeCAD</a> (or cad in general) - <a href="https://melonbread.xyz/tags/Rust-lang" rel="nofollow noopener" target="_blank">#Rust-lang</a> (I can run <code>cargo install</code> just fine) - <a href="https://melonbread.xyz/tags/PowerShell" rel="nofollow noopener" target="_blank">#PowerShell</a> (eh, don't care that I don't get this one) - <a href="https://melonbread.xyz/tags/SecureBoot" rel="nofollow noopener" target="_blank">#SecureBoot</a> - <a href="https://melonbread.xyz/tags/Treafik" rel="nofollow noopener" target="_blank">#Treafik</a> This is probably more but man it kills me I can not wrap my head around these.

mortI'm trying to figure out this whole using Microsoft Windows thing because I want to try to compile my game for <a href="https://floss.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>But I'm encountering an issue trying to install cap'n proto: a file <a href="https://floss.social/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a> is looking for existsSomehow the fact that the file exists makes CMake not find itT_T<a href="https://floss.social/tags/windowsdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#windowsdev</a>

YavoProbably the better crash-course on CFLAGS for us newbies. It did solve my confusion.<a href="https://linuxreviews.org/Optimized_gcc_compiling_(cflags/cxxflags,_distcc,_ccache)" rel="nofollow noopener" translate="no" target="_blank">https://linuxreviews.org/Optimized_gcc_compiling_(cflags/cxxflags,_distcc,_ccache)</a><a href="https://fosstodon.org/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a> <a href="https://fosstodon.org/tags/compiling" class="mention hashtag" rel="nofollow noopener" target="_blank">#compiling</a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>

YgorFair enough.<a href="https://github.com/emilk/egui/blob/main/deny.toml#L42" rel="nofollow noopener" translate="no" target="_blank">https://github.com/emilk/egui/blob/main/deny.toml#L42</a><a href="https://floss.social/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> <a href="https://floss.social/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://floss.social/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a> <a href="https://floss.social/tags/egui" class="mention hashtag" rel="nofollow noopener" target="_blank">#egui</a>

pseyfertTIL <a href="https://cmake.org/cmake/help/latest/command/string.html#json" rel="nofollow noopener" translate="no" target="_blank">https://cmake.org/cmake/help/latest/command/string.html#json</a> <a href="https://chaos.social/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a> has a json serialization helper function

Mattias Wadmancmake is trying to tell me something <a href="https://fosstodon.org/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a> <a href="https://fosstodon.org/tags/cake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cake</a>

Baudouin FeildelJust dropped a merge request to add support for Rust into CMake. Time to go to bed now I guess 😴 🛌 <a href="https://gitlab.kitware.com/cmake/cmake/-/merge_requests/11109" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.kitware.com/cmake/cmake/-/merge_requests/11109</a><a href="https://diaspodon.fr/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> <a href="https://diaspodon.fr/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a>

ApolloWhat IDE or editor do you use on <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> for <a href="https://social.tchncs.de/tags/Cpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cpp</a> development with <a href="https://social.tchncs.de/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a>? I am currently using VSCode with the C/C++ Extension Pack and CMake Tools Extensions. They work great for the most part but I don't like the route Microsoft goes and I'd rather have a working alternative that doesn't suck.I tried <a href="https://social.tchncs.de/tags/vim" class="mention hashtag" rel="nofollow noopener" target="_blank">#vim</a>, which works for the most part, just some copy pasting is a bit cumbersome.Any suggestions for a good alternative?

pseyfertAhaha, the <a href="https://chaos.social/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> crate even ships a <a href="https://chaos.social/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a> function to print the version number to avoid parsing cmake --version and still fails on the colour escape sequence that cmake adds (actually the code only turns off colours). And it even sets CLICOLOR, just not CLICOLOR_FORCE (which I use for tools that wrongly assume no-tty=parsing).Now I'm nerd sniped if the crate shouldn't ship a cmake version comparison function and let cmake pass/fail instead of print.

INCD021So after fighting <a href="https://mastodon.gamedev.place/tags/ImGui" class="mention hashtag" rel="nofollow noopener" target="_blank">#ImGui</a> and not getting it to work, I've switched to <a href="https://mastodon.gamedev.place/tags/raygui" class="mention hashtag" rel="nofollow noopener" target="_blank">#raygui</a> and it worked right away. I think I'm just not used to <a href="https://mastodon.gamedev.place/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a> and VS Code setup yet, and I've been pampered way too much over the past decade with nice looking IDEs. They are good, but also hide a lot of what is going on under the hood. So it's nice having to be so explicit. Also why I'm turning to C++ again. Not too much magic!

mgorny-nyan (on) :autism:🙀🚂🐧Jeżeli piszecie bibliotekę, naprawdę powinniście unikać <a href="https://pol.social/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a>. To, w jaki sposób zaprojektowano ten system budowania sprawia, że wasz projekt staje się od niego zależny. Praktycznie uniemożliwia to przejście na inny system budowania w przyszłości bez sprawiania sporych kłopotów istniejącym użytkownikom. A jeżeli zdecyduje się wspierać wiele systemów budowania, to wówczas wasi użytkownicy będą blokować innych.A wszystko przez to, że CMake używa niestandardowego systemu odkrywania zależności, który jest praktycznie niezgodny ze wszystkim innym, i tak złożony, że powtórna implementacja w innym systemie budowania jest szalenie skomplikowana. Więc kiedy inni zaczną polegać na tym, że wasza biblioteka instaluje pliki konfiguracji CMake (a jest to nieuniknione, bo po prostu tak się używa CMake), to wówczas nie będziecie mogli przestać ich instalować, nie psując ich projektów. A jeżeli będzie chcieli dalej je instalować przy pomocy innego systemu budowania, to powodzenia.A jeżeli CMake to jedna z wielu opcji, które wspieracie, to niektórzy z waszych użytkowników zaczną przypadkowo zakładać, że mogą polegać na CMake. A na tym stracą wszyscy inni, którzy budują waszą bibliotekę przy pomocy innego systemu budowania, i nie będą mogli zbudować tego projektu, który zaczął polegać na CMake. A potem jest już tylko gorzej — coraz więcej dystrybucji jest zmuszonych do budowania waszej biblioteki przy pomocy CMake, i coraz więcej projektów polega na tym, że "wszyscy" używają CMake…Używajcie systemu budowania <a href="https://pol.social/tags/Meson" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meson</a> — jest bardziej przejrzysty i lepiej przemyślany. A do wyszukiwania bibliotek używajcie plików pkg-configa; są proste i przenośne.<a href="https://pol.social/tags/WolneOprogramowanie" class="mention hashtag" rel="nofollow noopener" target="_blank">#WolneOprogramowanie</a>

mgorny-nyan (he) :autism:🙀🚂🐧If you're writing a library, you should really avoid <a href="https://social.treehouse.systems/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a>. CMake is designed to lock you in. As in, once you release a <a href="https://social.treehouse.systems/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> project using CMake, you can't switch to another build system with causing real trouble to your users. And if you support multiple build systems, as soon as you start supporting CMake, some of your users are going to start locking everyone else in.That's because CMake uses a custom package discovery mechanism that's hardly compatible with anything else, and that is so complex that it's very hard to reimplement it with any other build system. So when others start relying on the CMake config files being installed (and they naturally will, since that's how CMake does things), you can't stop installing them without actually breaking stuff. And if you want to preserve them without actually using CMake, well, good luck with that.And if CMake is one of the options you support, then some of your consumers will accidentally start relying on it anyway. And this will be much worse for everyone, because now their projects won't work for people who build your project with any other build system. Which in turn will force more projects to use CMake anyway. Which in turn will make more people rely on CMake being used…Use <a href="https://social.treehouse.systems/tags/Meson" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meson</a> as the build system, it's clean and not designed to lock you in. Use pkg-config for library data; it's simple and portable.<a href="https://social.treehouse.systems/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

mgorny-nyan (he) :autism:🙀🚂🐧Once again, a <a href="https://social.treehouse.systems/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a> project is breaking compatibility with systems that aren't building its dependencies via CMake (but are using Meson instead). Because why use pkg-config when you can use generated CMake configs instead?<a href="https://github.com/Blosc/c-blosc2/issues/687" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Blosc/c-blosc2/issues/687</a>EDIT: looks like this was done to accommodate <a href="https://social.treehouse.systems/tags/VcPkg" class="mention hashtag" rel="nofollow noopener" target="_blank">#VcPkg</a>. Surely accidental, but why not bash <a href="https://social.treehouse.systems/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> for breaking Linux packages anyway?<a href="https://github.com/Blosc/c-blosc2/pull/682" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Blosc/c-blosc2/pull/682</a><a href="https://social.treehouse.systems/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a> <a href="https://social.treehouse.systems/tags/packaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#packaging</a>

KawaoneechanWhy do I consistently have trouble using <a href="https://mas.to/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a>? Am I stupid?<a href="https://mas.to/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Generic PersonSo <a href="https://social.linux.pizza/tags/Tenacity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tenacity</a> on <a href="https://social.linux.pizza/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> isn't much effort to get running, but it does involve a lot of patience if compiling on an 11 year old laptop (I should be getting a new one soon).The changes? We just add /usr/local/lib to our link directories in <a href="https://social.linux.pizza/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMake</a>, fix compilation for FAT filesystem detection, and then we're all good to go! Then everything else comes together. After all, <a href="https://social.linux.pizza/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> and FreeBSD are similar enough to the point that we don't need to care much about the differences.And in case you wonder why we need to detect a FAT filesystem, if we were to allow it, you would immediately find out why we do it. AUP3 projects get large in size, and FAT filesystems are NOT equipped to handle them. Well, exFAT should be OK, but that's the only FAT filesystem that should work.

HaraldEat your own dog food, they say.Which I did, using my currently preferred build system, pythonbuilder. And a small but very convenient helper function was added.<a href="https://harald.codeberg.page/pythonbuilder/@main/apidoc/pbutil.html" rel="nofollow noopener" translate="no" target="_blank">https://harald.codeberg.page/pythonbuilder/@main/apidoc/pbutil.html</a>home page: <a href="https://codeberg.org/harald/pythonbuilder" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/harald/pythonbuilder</a><a href="https://nrw.social/tags/pythonbuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#pythonbuilder</a> <a href="https://nrw.social/tags/buildmachine" class="mention hashtag" rel="nofollow noopener" target="_blank">#buildmachine</a> <a href="https://nrw.social/tags/bashbuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#bashbuilder</a> <a href="https://nrw.social/tags/buildsystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#buildsystem</a> <a href="https://nrw.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwaredevelopment</a> <a href="https://nrw.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://nrw.social/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://nrw.social/tags/make" class="mention hashtag" rel="nofollow noopener" target="_blank">#make</a> <a href="https://nrw.social/tags/gradle" class="mention hashtag" rel="nofollow noopener" target="_blank">#gradle</a> <a href="https://nrw.social/tags/ant" class="mention hashtag" rel="nofollow noopener" target="_blank">#ant</a> <a href="https://nrw.social/tags/blt" class="mention hashtag" rel="nofollow noopener" target="_blank">#blt</a> <a href="https://nrw.social/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmake</a>

Recent searches

Search options

Administered by:

Server stats:

#cmake