Conan Alternatives

conan reviews and mentions

• Conan: Your Embedded Cross-Compilation Champion
  2 projects | dev.to | 13 Jul 2024

  include(FetchContent) FetchContent_Declare(conan URL https://github.com/conan-io/conan/releases/download/2.3.2/conan-2.3.2-linux-x86_64.tgz ) FetchContent_Populate(conan) if (conan_POPULATED) set(CONANEXE ${conan_SOURCE_DIR}/conan) set(CONAN_AVAILABLE TRUE) endif()

• Are We Modules Yet?
  3 projects | news.ycombinator.com | 1 May 2024

  Silly question: What's the difference between C++20 modules and https://conan.io? (Google was vague, and ChatGPT, you know, sometimes makes things up so I rather ask fellow humans...)

• The xz attack shell script
  5 projects | news.ycombinator.com | 2 Apr 2024
• My first Software Release using GitHub Release
  6 projects | dev.to | 24 Nov 2023

  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.

• Anyone else frustrated with Conan2?
  3 projects | /r/cpp | 31 Aug 2023

  Hi u/instinkt900, Conan maintainer here. Thanks for your feedback! Please remember that we actively monitor and respond to our issue tracker on GitHub (https://github.com/conan-io/conan/issues/new/choose), we’d love to hear about your specific use cases or pain points, so that we can improve your experience and that of other users. The motivation behind most of the updates in Conan 2.0 was precisely feedback from the community, and to improve our ability to continue delivering features in the constantly changing C++ ecosystem. We can certainly do this at a quicker pace, with some exciting new features recently released and in the pipeline: package metadata, transparent backup of downloaded package sources, cache least-recently-used cleanup, etc. A lot of the big decisions that we took for Conan 2.0 were taken with consensus from expert users and contributors (https://conan.io/tribe) and https://github.com/conan-io/tribe. Some specific workflows may not have 1:1 replacements in Conan 2.0, and are likely to affect some of the “less travelled roads” of Conan 1.x, including some features that were always marked as experimental. We are happy to hear feedback so that we can best satisfy these use cases. Conan 2.0 also includes a more sophisticated API to cover cases where the built-in integrations may not satisfy users needs. For what it’s worth - we have also heard very positive feedback from users about how Conan 2.0 simplifies their workflows when compared to Conan 1.x. The C++ tooling ecosystem is fragmented and moves at different speeds, including our users. So it’s always a fine balancing act, but we don’t want to leave anyone behind! An example is Conan Center - over 90% (~1200) of all recipes have been migrated to support Conan 2.0, while still maintaining compatibility with Conan 1.x, precisely to avoid breaking users that are still on Conan 1.x.

• OpenSSL as a git submodule?
  1 project | /r/cpp_questions | 24 Aug 2023

  Solution: don't use git submodules - use a package manager like Conan or vcpkg.

• Writing a Package Manager
  3 projects | news.ycombinator.com | 23 Aug 2023

  The closest thing we have at the moment is conan[1]. It’s a cross platform package manager that attempts to implement “toolchains”, whereby different build systems can be integrated[2]. This is a big problem with package management in C/C++, there’s no single, standardised build system that most projects use. There isn’t even a standardised compiler! So when hosting your own packages using Conan, often you need to make sure you build your application for three different compilers, for three different platforms. Sometimes (for modern MacOS) also for two different architectures each.

  If you control the compiler AND build system you can get away with just one package for most cases. This true for Microsoft’s C/C++ package manager, NuGet[3]

  Historically, the convention has been to use the package manager of the underlying system to install packages, as there are so many different build configurations to worry about when packaging the libraries. The other advantage of using the system package manager is that dependencies (shared libraries) that are common can be shared between many applications, saving space.

  [1] https://conan.io/

• Building libraries, when it's Not going as planned
  1 project | /r/cpp_questions | 4 Aug 2023

  Anyway, the problems are today starting to get fewer, as more an more adopt standard cross-platform portable build systems, a.k.a. CMake and package managers such as vcpkg or Conan. Together this will take care of building, installing, linking and using the entire dependency tree.

• Help with Building Crypto++
  1 project | /r/cpp_questions | 28 Jul 2023

  Simply use a package manager: Crypto++ is available on both vcpkg and Conan.

• Is there an easy installer for wxWidgets like there is for Qt?
  1 project | /r/cpp_questions | 6 Jul 2023

  If you want a specific version or provide a more integrated workflow that is easier to use across platforms and among many developers, use a package manager like vcpkg or Conan.

• A note from our sponsor - Judoscale
  judoscale.com | 29 Apr 2025

  Judoscale integrates with Django, FastAPI, Celery, and RQ to make autoscaling easy and reliable. Save big, and say goodbye to request timeouts and backed-up task queues. Learn more →