DPP VS cmake-init

For me it just fails on dpp wrap file not containing a valid URL. And if I change it to https://github.com/brainboxdotcc/DPP, it fails on the repo not containing a meson.build file. And if I comment out the dependency it fails due to non-existent include/ directory. And if I comment that out, it succeeds just fine.

Sure, the D++ Discord bot library is a good example of an implementation of REST in C++. I wouldn't say it's particularly modern as it doesn't make a lot of use of modern C++ features such as constexpr, string_view and so on, but it's not too bad.

Looking quickly you'll want to use https://github.com/brainboxdotcc/DPP/blob/master/library-vcpkg/CMakeLists.txt

I've been working for many months (actually over a year now) on creating and maintaining the D++ Discord API Library (aka DPP) making it lightweight and scalable for my needs.

Out of curiousity; what does this library offer that, say, a mature library like DPP (https://github.com/brainboxdotcc/DPP) doesn't offer?

https://github.com/friendlyanon/cmake-init This is how you do CMake properly. If you deviate from its install rules you are highly likely to do something wrong.

CMake itself is as declarative as a build systems need to be. For anything nontrivial, these "declarative" solutions all fall apart. Just use https://github.com/friendlyanon/cmake-init, learn CMake and you won't have any issues.

If you want something with a (mostly) Just Works experience then just use https://github.com/friendlyanon/cmake-init

For CMake basics check out the official "Getting started" tutorial: https://cmake.org/cmake/help/latest/guide/tutorial/index.html, as well as Introduction to Modern CMake. You can also get inspired by the CMake project generator cmake-init

You can just use https://github.com/friendlyanon/cmake-init to get a CMake + Conan C project ready to go with a short little command: cmake-init --c -e -p conan coolio