FunctionalPlus VS cxx-static-shared-example

Hoogle is really amazing!

Inspired by it, I implemented something similar for FunctionalPlus (a functional-programming library for C++): https://www.editgym.com/fplus-api-search/

I'd love to see more projects taking this path too. :)

You can get a feel for it on its api search site: as an example, enter these queries:

I use a library called FunctionalPlus daily.

As idiomatic, I will try to adopt as much as possible purely functional programming in C++ by using https://github.com/Dobiasd/FunctionalPlus . Do you have by any chance any alternative suggestion?

Any project CML file that is more complex than this is mismanaged and needs fixing asap. There is absolutely no reason to make CML files describing requirements of a library substantially more complex other than if you have a vendetta against yourself, package maintainers and your users.

FunctionalPlus - 30 lines for usage requirements + 60 for install rules: just simple commands creating a target, setting properties and defining install rules. Hmm, nothing unholy here.

Another option is to use a superbuild CML where you can do all the nasty, platform specific things. Example of a superbuild CML.

You can copy this project structure: https://github.com/Dobiasd/FunctionalPlus

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.