conan-center-index VS Vcpkg

Conan is a package manager for C/C++. See: https://conan.io/.

The way it works is that you can provide "recipes", which are Python scripts, that automate the process of collecting source code (usually from a remote Git repository, or a remote source tarball), patching it, making its dependencies and transitive dependencies available, building for specific platform and architecture (via any number of build systems), then packaging up and serving binaries. There's a lot of complexity involved.

Here are the two recipes I mentioned:

libcurl: https://github.com/conan-io/conan-center-index/blob/master/r...

OpenSSL v3: https://github.com/conan-io/conan-center-index/blob/master/r...

Now, for the sake of this thread I want to highlight three things here:

- Conan recipes are usually made by people unaffiliated with the libraries they're packaging;

- The recipes are fully Turing-complete, do a lot of work, have their own bugs - therefore they should really be treated as software comonents themselves, for the purpose of OSS clearing/supply chain verification, except as far as I know, nobody does it;

- The recipes can, and do, patch source code and build scripts. There's supporting infrastruture for this built into Conan, and of course one can also do it by brute-force search and replace. See e.g. ZLib recipe that does it both at the same time:

https://github.com/conan-io/conan-center-index/blob/7b0ac710... -- `_patch_sources` does both direct search-and-replace in source files, and applies the patches from https://github.com/conan-io/conan-center-index/tree/master/r....

Now, good luck keeping track of what's going on there.

https://github.com/conan-io/conan-center-index there's 200+ PR that need reviewing :) we add community reviewers fairly often

As for ffmpeg it was last updated 10 days ago https://github.com/conan-io/conan-center-index/commits/master/recipes/ffmpeg/all :)

Indeed others in your situation have chosen to remain a bit longer on Conan 1.x - rest assured, every single pull request in Conan Center still requires full compatibility with Conan 1.x. u/miss_minutes, I'm surprised to hear that downgrading to the latest stable 1.x version has caused issues for you. I'd be very interested in learning about this so that we can help, please feel free to open an issue in GitHub with more details at https://github.com/conan-io/conan-center-index/issues/new/choose, and tag me @jcar87, and we'll gladly look into this.

https://github.com/conan-io/conan-center-index if you want to contribute migration of that recipes that would be amazing

This is a more complicated recipe https://github.com/conan-io/conan-center-index/blob/master/recipes/pcapplusplus/all/conanfile.py

It's available in Conan too https://github.com/conan-io/conan-center-index/tree/master/recipes/crowcpp-crow though it's not well maintained so no promises if it's working

This post on github contains a list of packages supported by conan 2.0, its also kept up to date https://github.com/conan-io/conan-center-index/discussions/16196

2) Go to https://conan.io/center/ and search for nlohmann, click the first hit.

I hope CMake and conan continue to be adopted by more CPP developers. But the future will tell.

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 .

CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message): Command failed: /usr/bin/cmake --build . --config Debug --target install -- -v -j25 Working Directory: /opt/vcpkg/buildtrees/hyperscan/x64-linux-dbg See logs for more information: /opt/vcpkg/buildtrees/hyperscan/install-x64-linux-dbg-out.log Call Stack (most recent call first): installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process) installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build) ports/hyperscan/portfile.cmake:22 (vcpkg_cmake_install) scripts/ports.cmake:147 (include) error: building hyperscan:x64-linux failed with: BUILD_FAILED Please ensure you're using the latest port files with `git pull` and `vcpkg update`. Then check for known issues at: https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+hyperscan You can submit a new issue at: https://github.com/microsoft/vcpkg/issues/new?title=[hyperscan]+Build+error&body=Copy+issue+body+from+%2Fopt%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md You can also sumbit an issue by running (GitHub cli must be installed): gh issue create -R microsoft/vcpkg --title "[hyperscan] Build failure" --body-file /opt/vcpkg/installed/vcpkg/issue_body.md

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

unless you want to use clang-cl since it renames the output to make it work for MSVC which in return breaks FindBoost in cmake and requieres https://github.com/microsoft/vcpkg/pull/27694 to fix it. I have touched enough of vcpkg build scripts to know what works and what doesn't and the b2 build is one of the corners I strongly dislike.

And then there's also Qt which has plugins. vcpkg Qt5 is nice enough to copy the plugins for you, but not with Qt6. The official answer seems to be "use windeployqt". So I do, and it copies plugins fine. But sqlite doesn't work, despite the plugin sqldrivers/qsqlite.dll being in the right location. Turns out that neither vcpkg or windeployqt copy sqlite3.dll. I switched to static libraries after that, it's a lot slower to link, clang doesn't work for some reason (but clang-cl does) but at least I don't have to worry about DLLs.