Since binary compatibility is not guaranteed, it is not safe to individually export packages.Providing an easy way to export a subset of them will enhance user experience. The vcpkg root may have a variety of packages built and many of them might be unrelated to the current task.For the "end-developer", this makes the consumption of C++ libraries the same as C# ones. In an enterprise environment which focuses on C#, the dedicated acquisition team can create the NuGet packages with vcpkg and provide them to the other developers. Providing a way to create NuGet packages provides great value to those customers.
Customers who are working on a C# project that has a few dependencies on C++ and just want those dependencies to be satisfied in the most automatic way possible. Easy consumption in Visual Studio for NuGet usersĬustomers have requested C++ NuGet packages to integrate into their project. explicitly desired, like in the development of a game where libraries and their versions are sealed for a particular release, never to be modifiedĭ. not a concern, like in a short term project or assignment. Use vcpkg for the build, then put the binaries in an installer and distribute the installerĬonsuming the libraries outside of vcpkg forfeits the ability to install new libraries or update existing ones, but this can be:. Use vcpkg for the build, then host the binaries in a website (similarly to nuget). However, users need the ability to build the libraries and then use them outside of and independently of vcpkg. Vcpkg currently handles cases where you have a vcpkg enlistment on your machine and use it for acquiring libraries and integrating into Visual Studio, CMake etc. Therefore, having the ability to build them and then distribute the binaries can save a lot of time. Libraries like Qt can take a very long time to build (5+ hours). Therefore, there is value in enabling users to easily export ready-to-share binaries from vcpkg. CI Systems, in which developers want to quickly distribute their exact set of dependencies to a cloud-based farm of build machinesīuilding once and sharing ensures that everyone gets exactly the same binaries, isolates the building effort to a small number of people and minimizes friction to obtain them. Academic environments, in which the professor/teacher wants to build the required libraries and then provide them to all the students. Enterprise environments, in which there are dedicated teams to acquire libraries and then share them with other teams to consume them. 
Build once and shareĬustomers want to be able to build their set of required libraries once, and then distribute the resulting binaries to all members of the "group".
0 kommentar(er)
