prorab VS cxx-static-shared-example

Take a look at https://github.com/cppfw/prorab it is a framework for simplifying makefiles, perhaps with it your makefiles will be shorter than CMake files.

actually, I think what might be reasonable to do is to add a check into prorab.mk that it is run with GNU make. Created issue https://github.com/cppfw/prorab/issues/69

same here, plus https://github.com/cppfw/prorab

In case you decide to go with pure GNU make I can suggest a non-recursive makefiles template library https://github.com/cppfw/prorab.

The only thing is that my own build system is GNU make-based, so it's syntax is also not easy :P.

Anyone can create a library using cmake-init. This example goes into a little more detail and while it's for C++, the very same things apply sans a single target property on the library.

Thanks, I noticed a project friendlyanon/cxx-static-shared-example that have feature I didn't used.

https://github.com/friendlyanon/cxx-static-shared-example explains how to do libraries correctly, https://github.com/friendlyanon/cmake-init gives you a template that's ready to go. If something is not clear, ask away.

Here is an example going deeper into how to create a shared library using CMake: https://github.com/friendlyanon/cxx-static-shared-example You'd have to do these regardless of CMake, this just shows how to do it with it.

This example is more focused on explaining on the what and why.

Or if you are also packaging .deb then you're going to need a toolchain anyway, you can put these variables there as well.

To learn how to write a CML that is ideally written to be easy for both consumers building the library, developers developing the library and consumers vendoring the library via add_subdirectory (which will be a very very important thing to do in the near future), please check out this educational example repository https://github.com/friendlyanon/cxx-static-shared-example

This repo will show you how to make your project CML for an easy to (re)use library that supports packaging.

CMake's what you want. You need to know how separation of concerns applies when it comes the lists files. Resources in general suck, the CMake docs are not really discoverable, but are very good otherwise. You can get a handle of how things are supposed to be put together here.

cxx-static-shared-example - 50 lines for requirements + however many for sources + 60 for install rules: now this is a library that builds some artifacts. Still extremely simple and straightforward.