3 ms·

Digging around the announcement a bit, I'm having a hard time seeing why I might prefer this over Conan[1], and I'm not seeing anything about how I can stand up

Digging around the announcement a bit, I'm having a hard time seeing why I might prefer this over Conan[1], and I'm not seeing anything about how I can stand up my own private repository for vcpkg, which is what I am about to do with Conan. Can anyone sound off (or link a page where someone has done so) on what might tip someone toward this over Conan or vice versa? [1](https://www.conan.io/ https://www.conan.io/)

ihattendorf 9y ago
vcpkg has an FAQ[1] regarding this, if someone could find one from the other perspective I think that would be helpful. Personally, I prefer their integration with CMake, letting me `find_package(spdlog 0.16 REQUIRED)` allowing others to point to their own version with `-Dspdlog_DIR=...`. [1] https://github.com/Microsoft/vcpkg/blob/master/docs/about/faq.md#why-not-conan https://github.com/Microsoft/vcpkg/blob/master/docs/about/fa...
- hoistbypetard 9y ago
  Thanks. It looks like at least the third bullet has been reconsidered, based on this announcement. But I think the front matter on that section gives (at least for what I'm after) a pretty good start on an answer to my question. They aim to version all libraries together as a platform (like, say, homebrew or yum+rpm). Where Conan aims to behave a little more like what I'd term "pypi for C++". That is, if I'm reading this correctly, and I'm not yet certain that I am. One thing that I want to do, and it's clear to me how I'd do it with conan (or pip) but not yet clear to me how I'd do it with vcpkg, is have a version of a package that's available in a public repository also be available in my internal repository with some added private patches, and have my version "win" for my projects. Our recurring need for this is when we're building out patches that we want to have incorporated upstream but aren't ready to do that yet for one of many reasons.
pjmlp 9y ago
It doesn't need Python. My C++ compiler is good enough. I don't like package managers that force me to install a programming language just to use them.

ihattendorf 9y ago

vcpkg has an FAQ[1] regarding this, if someone could find one from the other perspective I think that would be helpful. Personally, I prefer their integration with CMake, letting me `find_package(spdlog 0.16 REQUIRED)` allowing others to point to their own version with `-Dspdlog_DIR=...`. [1] https://github.com/Microsoft/vcpkg/blob/master/docs/about/faq.md#why-not-conan https://github.com/Microsoft/vcpkg/blob/master/docs/about/fa...

hoistbypetard 9y ago
Thanks. It looks like at least the third bullet has been reconsidered, based on this announcement. But I think the front matter on that section gives (at least for what I'm after) a pretty good start on an answer to my question. They aim to version all libraries together as a platform (like, say, homebrew or yum+rpm). Where Conan aims to behave a little more like what I'd term "pypi for C++". That is, if I'm reading this correctly, and I'm not yet certain that I am. One thing that I want to do, and it's clear to me how I'd do it with conan (or pip) but not yet clear to me how I'd do it with vcpkg, is have a version of a package that's available in a public repository also be available in my internal repository with some added private patches, and have my version "win" for my projects. Our recurring need for this is when we're building out patches that we want to have incorporated upstream but aren't ready to do that yet for one of many reasons.

pjmlp 9y ago

It doesn't need Python. My C++ compiler is good enough. I don't like package managers that force me to install a programming language just to use them.