cmkr VS kangaru

Been using https://cmkr.build/ for a while now, its great and also declarative.

I would like to counter with a project I’ve been working on: https://cmkr.build. Unfortunately writing good CMake is extremely repetitive and there is definitely room for a generator that has sane defaults.

You are trying to use it the wrong way it seems, the point of CMakeLists.txt is that you only maintain that and nothing else. If you have changes in there then it will re-generate the project for you when it starts building. Adding files via IDE is not supported and is not really the point, there used to be a time where I primarily worked with VS solutions but the more I dove into the open source space the more it became clear that its the worst way of doing it. You just have to get used to a different workflow, the benefit is that your project can be in theory now compiled on all sorts of systems and not just with VS. If CMake is too much to handle perhaps give https://cmkr.build/ a try, it hides a lot of the CMake madness behind its toml specification, been using it for a while now, its great.

https://cmkr.build/ its pretty straight forward and been using it for some time now, can only highly recommend it.

Currently working on https://github.com/build-cpp/cmkr

I started working on https://github.com/build-cpp/cmkr to remedy this, but other similar solutions exist.

I invite you to take a look at https://github.com/build-cpp/cmkr, it makes this even easier ^

I’ve been working on cmkr, a modern build system based on CMake and TOML.

Definitely! I would recommend using cmake because it’s easy to generate a compile_commands.json. I’ve been working on https://build-cpp.github.io/cmkr to make the transition as smooth as possible.

This Fruit library is still on my TO-DO to review and try, but there is one other library that I wanted to try first, and it's called Kangaru. Both are DI injectors, but I can't say much more about them yet.

For example, in my game engine, the service configuration is in separated headers, and only the places that I'm using the library directly need those headers. See the page 13. Structuring Projects, this is where I'm talking about it.

Not lately, but I plan to get back into it. I'm making kangaru, a dependency injection container for C++ that reflects on constructor parameters to wire the classes together.