cmake-init-conan-example VS Vcpkg

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.

5.4.5 can be compromised

https://github.com/microsoft/vcpkg/issues/37197

vcpkg may expire assets after 1.5 years, so achieve long-term reproducibility you will need to cache your dependencies.... Somewhere. Not sure what the expected solution is.

https://github.com/microsoft/vcpkg/pull/30546#issuecomment-1...

There were various approaches recommended depending on our language and ecosystem. My classmates who developed using Node.js were recommended npm, and PyPI or poetry for Python. Since my program is written in C++, I was recommended to look into one of vcpkg or conan, but I ultimately did not use either package manager.

Which dependencies are not in vcpkg? We can ask them to add it. It’s pretty easy just open an issue there https://github.com/microsoft/vcpkg/issues .

./vcpkg search netcdf gdal[netcdf] Enable NetCDF support minc 2.4.03#3 MINC - Medical Image NetCDF or MINC isn't netCDF minc[minc1] Support minc1 file format, requires NETCDF netcdf-c 4.8.1#2 A set of self-describing, machine-independent data formats that support th... netcdf-c[dap] Build with DAP remote access client support netcdf-c[hdf5] Build with HDF5 support netcdf-c[nczarr] Build with NCZarr cloud storage access support netcdf-c[nczarr-zip] Build with NCZarr ZIP support netcdf-c[netcdf-4] Build with netCDF-4 support netcdf-c[platform-default-features] Enable platform-dependent default features netcdf-c[tools] Build utilities netcdf-cxx4 4.3.1#4 a set of machine-independent data formats that support the creation, acces... The result may be outdated. Run `git pull` to get the latest results. If your port is not listed, please open an issue at and/or consider making a pull request. - https://github.com/Microsoft/vcpkg/issues

The hyperscan update to vcpkg seems to have happened from 5.4.0 to 5.4.2 in this commit on Apr 20.

Dear Fictrac team, I am hoping to install Fictrac in our windows 11 x64 laptop (Visual Studio 2019, cMake 3.26.4). I followed the installation guideline on github page fictrac and used the latest vcpkg

This works fine if one wants to do stuff like clang main.cpp -lvulkan, or even find_package(Vulkan REQUIRED) in CMake, but it doesn't define VULKAN_SDK, and therefore doesn't work with vcpkg's Vulkan support, for instance. A fair bit of Vulkan development, tutorials, etc. assume that the entire SDK is installed, as-is.