cmake-init-conan-example VS icecream

I haven't really used conan but you should not use the cmake generator, you should use the CMakeDeps and CMakeToolchain generators instead. That might solve your problem, after all there is a reason why the cmake generator is being deprecated. Check this for an example: https://github.com/friendlyanon/cmake-init-conan-example

Use a package manager. This example shows how to use vcpkg to get json-c. You can do the same using Conan as well.

You ought to call Conan before configuring. Take a look at this example.

Conan and vcpkg are the only options. I use them both, depends on what kinds of dependencies I want to pull. vcpkg is easier to setup custom one-off dependencies with using overlay ports, while Conan is faster at things if your profile fits one that has a pre-built binary in CCI. Both are trivial to integrate with a CMake project, see these examples for Conan and vcpkg.

More details in this example project.

I have an example for Conan integration that I'm planning on revisiting, since it was made when I knew less about Conan. If you are interested in a concrete example, you can check it out later.

Integrating with Conan is already pretty straightforward, you just need a short script to glue things together via the Conan provided CMake utility.

You can check out the CI for this example project. It doesn't yet have caching for Conan setup, but Qt has prebuilt binaries in the CCI anyway, so that's not really that big of a deal.

The CMake scripts could definitely use improvement. Here is an example using Conan that also installs fmt. The shell scripts can also be entirely replaced with CMake presets, also examplified in the earlier link.

Or Conan + CMake. In fact, I would much prefer to use Conan in a company environment, but vcpkg is top notch for open source. Not to say Conan is bad at that, not even close, but its features are excellent to get companies to move to package managers.

Related

https://github.com/icecc/icecream - another option that does what distcc does, but aimed at a somewhat different use case.

https://ccache.dev/ - a similar idea but provides caching of build outputs instead of distributing builds. You can use it together with distcc to achieve even better performance.

Of course! The github readme provides a lot of info - https://github.com/icecc/icecream

If you like distcc, did you ever give icecc a try?

https://github.com/icecc/icecream

I never had the time to set it up properly, but by the looks of it, it should be even better.

I would like to have a icecc setup I can vpn into. It seems that with normal configs the clients can talk to the scheduler, but the scheduler cant connect to the clients as it tries to connect to the device running the openvpn server not the one behind it. How could I make my openvpn clients appear almost as physical devices on the network, with unique IP's that local devices can connect to; or if that is unnecessary how could I solve this?

Glad to see a new release on this! I've read worrying news about the state of icecc, and the followup uncertain news on sccache, so I hope at least some part of the tooling is in a good shape.

I always wanted to try to use cmake-conan so I could let Conan grab all packages but have a neat cmake script being in charge of what gets built when. Also, this would allow me to easily switch between CMake fetchcontent and Conan packages that may or may not be stashed automatically on a local Artifactory server. Secondly, since now all build requirements are stashed on a server and binary reproducible, you could concider adding icecream and ccache into the mix. (Try running a node one of your buildservers for massive speadups with icecream) This however does require a reproducible build environment (by configure script) which conan again is really good in.