I’m writing an app, which is using blake3, libsodium, libwebsockets(git master, because I have a patch upstream not in the release yet to support IPV6 PREFER_SRC_PUBLIC), google test, and a custom library.
Libsodium uses autotools configure files.
All of these are a bit esoteric and not normally installed on Linux machines, if they are they are often old versions.
So I went with a superbuild.
From the main superbuild, to each ExternalProject_Add function
I am doing
And then for my app that needs to link all those libraries I am doing
It’s basically making everything build static libs in like a standard install prefix in the build directory, and letting all of the dependent libs install themselves into a prefix I can later use to link with and use the standard include path with.
Not all the dependencies use native cmake, so I figure it is more reproducible to do that and then use find_library in my main project that needs to link.
Is that like non-standard, or clean enough?
It seemed to be the cleanest thing to do.
If I was using popular libraries, like openssl or gnutls, I’d just use the OS’s libraries.
For my own lib, I am just using what add_library exported, not going back to find_library.
Superbuilds seemed to be a common way to support libraries that use cmake natively, and ones that don’t. They also happen at configure time, so you can build libraries before having a build dependent on them.