xmake VS CPM.cmake

My usual comment shilling for xmake in any build system conversation, that's how much I like it : https://xmake.io/#/

There are other installation methods : https://xmake.io/#/guide/installation?id=macos

It's in the official Fedora and Arch repos and there is ppa for Ubuntu

In recent times I prefer Xmake[0] to CMake.

[0] https://xmake.io

I really like xmake for c++, not very similar to cargo but then c++ isn't very similar to rust.

I recommend xmake

you can try xmake. https://github.com/xmake-io/xmake

xmake nothing comes close

I like to pin GitHub dependencies using a commit hash, instead of a tag. You need a recent CPM.cmake file in your project for CPM to work.

C++20 brings std::format, improving C++ developer experience for formatting strings. If you have to use older standards, though, add fmtlib to your repo. It plays well with CMake and you can use CPM to add fmtlib to your project. The library supports many Rust format macro features, and makes code far cleaner when you need to do string interpolation with variables.

This is true for almost all projects but things are getting better. I use CPM for a couple of years now and get the experience desired

https://github.com/cpm-cmake/CPM.cmake

Yes, i found vcpkg terrible and FetchContent usually works way better. An amazing project is https://github.com/cpm-cmake/CPM.cmake, which automates FetchContent and makes dependencies mostly hassle free.

There's two completely different aspects to your question. 1) How to manage libraries in c++ without dying from cringe? I'd suggest you use cmake as the build system and grab library sources directly from GitHub using this tool: https://github.com/cpm-cmake/CPM.cmake 2) How to get apps that run under WSL to display windows-native windows? I'm not sure, but it's probably this: https://github.com/microsoft/wslg

At first, I wanted to install it using Vcpkg but I ended up using CPM.cmake instead. Why? Because with Vcpkg on some platform it is messing up the config and choose a version of Python used in Vcpkg instead of the one I wanted to use. It is not that hard to fix, but why bother when I can install the library in one line with CPM.cmake

set(CPM_DOWNLOAD_LOCATION ${CMAKE_BINARY_DIR}/CPM.cmake) file(DOWNLOAD https://github.com/cpm-cmake/CPM.cmake/releases/latest/download/cpm.cmake ${CPM_DOWNLOAD_LOCATION}) include(${CPM_DOWNLOAD_LOCATION})

We're using vcpkg - tried conan previously. I think both are good, but both of them have their own flaws. You can also go with something like https://github.com/cpm-cmake/CPM.cmake if you just want something quick for a small project.

May I introduce you to our CMake lord and savior, CPM? As long as there's a repo with a CMakefile.txt, it will build it.

this is also great https://github.com/cpm-cmake/CPM.cmake