Suchergebnisse
Suchergebnisse:
Conan brings C++ development and dependency management into the 21st century and on par with the other development eco-systems. We are currently designing this in to streamline the development of test programs for our products to help facilitate reuse and help our distributed teams develop the robust and efficient tests to guarantee the quality ...
- ConanCenter
Popular recipes. Just updated. New version. Conan is an open...
- FAQ
Conan is a package manager for C and C++ which aims to solve...
- ConanCenter
No, there's no package manager for C++ libraries. There are various ways to install C++ libraries, as with any other software: through your operating system's package manager, by building from a source tarball, or, in the case of proprietary software, by running some installation program.
- There seem to be a few though I've never used them. dds https://github.com/vector-of-bool/dds. cpm http://www.cpm.rocks/. conan https://conan.io...
- Conan is the clear winner today based on its 36+ GitHub contributors and the fact I found their Getting Started documentation to be easy enough to...
- No, there certainly isn't an official package manager for C/C++, but I'll give you a few suggestions to hopefully make your days better. First, I...
- The other answers have mentioned the competing solutions, but I thought I would add my experiences. I did some research into package managers and b...
vcpkg is a free C/C++ package manager for acquiring and managing libraries. Choose from over 1500 open source libraries to download and build in a single step or add your own private libraries to simplify your build process. Maintained by the Microsoft C++ team and open source contributors.
- Overview
- Why vcpkg?
- vcpkg features
- vcpkg compared to other package managers
- Get started with vcpkg
vcpkg is a free and open-source C/C++ package manager maintained by Microsoft and the C++ community. Launched in 2016, it helps developers migrate their projects to newer versions of Visual Studio. vcpkg has evolved into a cross-platform tool used by developers on Windows, macOS, and Linux. vcpkg has a large catalog of open-source libraries and ent...
•Over 2200 open-source libraries to choose from, or bring your own
•Consistent, cross-platform experience for Windows, macOS, and Linux
•Build dependencies from source as needed, with over 70 configurations in the box, and infinite customization for your specific requirements
•Avoid ABI incompatibilities between packages and your project
•Prevent version conflicts and diamond problems in your dependency graph
•It's enterprise-ready. C/C++ developers across many industries rely on it, including: finance, gaming, embedded/IoT, semiconductors, defense, and at Microsoft
Ports and triplets
A vcpkg port is a versioned build recipe that produces a package. The most common type of package is a C/C++ library consisting of headers, source code, and binaries. A triplet captures the target build environment (cpu, os, compiler, runtime, etc.) in a single, convenient name. vcpkg provides over 70 triplets by default, but you can also define your own. To install a package on your system, vcpkg runs the port's recipe file, which is a CMake script. The script might contain steps to download source code or to run a build on your system. During builds, vcpkg uses the information in your triplet to ensure that the produced package matches your desired configuration.
Binary caching
While vcpkg builds libraries from source whenever it's necessary, you can back up your built packages in a binary cache. This allows other developer machines or continuous integration runs to reference these prebuilt packages without running a new build every time. vcpkg determines if a rebuild is necessary by checking if the cache already contains a valid existing package when it attempts to install a package.
Manifests
You can declare your direct dependencies and add optional features or version constraints in a manifest file.
vcpkg compared to NuGet
NuGet is a .NET package manager that is often used for C/C++ development, particularly for MSBuild solutions that contain .NET projects. As a general rule, the Microsoft C++ team does not recommend using NuGet for C/C++ development because NuGet has several limitations: •Compilation flavors. Because NuGet cannot build packages from source on the fly, it is necessary to provide prebuilt binaries to match all possible Application Binary Interface (ABI) restrictions for all users. The user is responsible for correctly building packages. It's also difficult to distinguish between binaries due to the lack of relevant metadata. This results in the user putting architecture, operating system, and compiler information in the package name. This is undesirable because constraints on architecture, OS, and compiler information can't be enforced during package acquisition. •Binary vs. source. NuGet is designed from the ground up to provide relatively small, prebuilt binaries. Developers need to have access to the source code to ensure ABI compatibility, performance, integrity, and debuggability. •No NuGet PackageReference support. NuGet PackageReference is not supported for .vcxproj files and there isn't a plan to add it in the future due to technical and architectural differences between C++ and .NET MSBuild projects. This means NuGet C++ users won't benefit from features like the use of the global cache and referencing dependencies in simple MSBuild terms with access to conditional logic. •Transitive ABI tracking. vcpkg rebuilds open-source dependencies impacted by a change in a particular package. For example, if a new update is released for Boost, vcpkg rebuilds all of the dependencies of Boost, and libraries that depend on Boost, to ensure they still work. Pull requests to update libraries in the vcpkg repo are not merged until build-time conflicts are addressed.
vcpkg compared to system package managers
There are a wide variety of system package managers for Linux, macOS, and Windows that can be used to acquire and manage C/C++ libraries. These package managers are typically excellent choices for managing applications. But due to the generic nature of their support, they often fail to deliver features beneficial particularly for C/C++ developers. While your mileage will vary, and some system package managers do deliver some of these features, none have all of the following: •Redistributable developer assets: vcpkg can acquire redistributable developer assets to help with debugging. •Prebuilt packages vs. build from source: vcpkg can build packages from source based on your custom requirements. There is no need to deal with with prebuilt, pre-compiled packages to get them to work. •Catalog-wide versioning: vcpkg allows you to depend on a version set of compatible packages, rather than having to micromanage individual package versions. You can still do so as needed, but the default experience is designed to be easy to get started with. •Multiple copies of the same library on one system: You can have multiple copies of the same dependency installed on the same system with vcpkg, whereas system package managers may install one version to a single, system-wide location. This complicates things when you have multiple projects depending on different versions of a library. •Catalog size: Because vcpkg is specialized for C/C++, it has a very large C/C++ library catalog in comparison to system package managers, and it is actively maintained. In general, you are more likely to find useful and up to date libraries for C++ development. •Cross-platform support: System package managers provide packages locked to a particular system. If you need to target more than one operating system flavor, you'll need to find a different package manager for the second system. In contrast, vcpkg is a cross-platform package manager. So, you simply need to adjust your target builds accordingly. There are situations where a system package manager absolutely makes sense: •System package managers tend to do a good job providing and maintaining libraries specific to that system •Prebuilt packages should work out of the box on that system if your consuming project has a simple build configuration. •If you don't intend to do any cross-platform development, you won't run into operating system compatibility issues with a system package manager.
To try out vcpkg, use one of our introductory tutorials:
•Install and use packages with CMake
•Install and use packages with CMake in Visual Studio
•Install and use packages with MSBuild in Visual Studio
Vcpkg helps you manage C and C++ libraries on Windows, Linux and MacOS. This tool and ecosystem are constantly evolving, and we always appreciate contributions! If you've never used vcpkg before, or if you're trying to figure out how to use vcpkg, check out our Getting Started section for how to start using vcpkg.
Setup-free CMake dependency management. CPM.cmake is a cross-platform CMake script that adds dependency management capabilities to CMake. It's built as a thin wrapper around CMake's FetchContent module that adds version control, caching, a simple API and more.
