vcpkg

Содержание

Prioritized Backlog
Other Ideas (Unprioritized)

This page contains a prioritized backlog of upcoming vcpkg work and completion status. This will change over time as we adjust our planning and react to user feedback. Note that we cannot provide reliable timelines for these items at this time, but we are working on making our public communication process better - stay tuned!

Prioritized Backlog

Documentation overhaul
- Description: We have been getting lots of feedback about our documentation. There are a couple of areas where we need to brush up existing documentation, write new articles, and also make sure people find the articles relevant to their work. For the latter, we want to improve the internal search experience for our documentation. To avoid confusion about which documentation is correct, we want vcpkg.io to be treated as authoritative. We will provide the same kind of deep linking capabilities currently provided only on GitHub and use vcpkg.io in customer explanations of our behavior. We also want to review how we describe what an official vs. a community triplet is, since there seems to be some confusion about what target platforms x architectures vcpkg can support.
- Status: We are working on a plan for this experience, so we are still on the planning/design phase.
- Timeline: To be determined.
MSVC and other Windows tools available in vcpkg artifacts
- Description: Finish implementing vcpkg commands for the artifacts experience and make sure it synergizes well with ports. Fix known issues. Provide vcpkg artifacts for MSVC toolset and Windows SDK. Add MSBuild integration for vcpkg artifacts and tweak the experience for ports as well for a better experience in Visual Studio.
- Status: We have engineers at Microsoft assigned to each area for this and are actively working on this. Someone is working on finishing up the core command line experience for artifacts and cleaning up remaining bugs. Our top MSBuild expert is working on that integration. A third person is designing the MSVC artifact story. We have also been talking to the Windows SDK team about incorporating their NuGet package editions of their SDK into vcpkg artifacts at some point in the future, but we need to finish preparing the rest of the story so it's clear to them exactly how they should organize their packages to work with vcpkg.
- Timeline: To be determined.
New vcpkg experience in Visual Studio
- Description: vcpkg will be included for all Visual Studio C++ workloads. vcpkg will be localized for all the languages VS supports. Potentially some productivity features to make it easy to install and manage libraries from the IDE. vcpkg artifacts will also work in a VS context for MSBuild and Open Folder (including CMake) projects.
- Status: Our team has made some investments in this space. We have a special binary distribution of the vcpkg tool that we can add to VS installations. We are working on localization for different languages, as we need to support all languages VS supports to ship with the IDE. We are also exploring some productivity features, like quick action lightbulbs to help VS users install missing libraries. We are in the design phase for the Open Folder integration and the MSBuild integration is currently being coded. This work is still in flux and has been pushed back somewhat by the higher prioritization of vcpkg artifacts, which was introduced to the backlog at a later time.
- Timeline: To be determined.
vcpkg Visual Studio Code extension
- Description: vcpkg will be provided for VS Code users via an extension. The extension will require the Microsoft C++ extension to work well, and probably the CMake Tools extension if you intend to use vcpkg with CMake in VS Code. Similar functionality planned as the VS integration work item above.
- Status: Same progress as VS in terms of producing the vcpkg tool binary and localization. We plan to ship the VS Code extension no earlier than the VS experience.

Other Ideas (Unprioritized)

vcpkg artifacts integration in VS Code - use vcpkg to install a compiler, debugger, and other tools that VS Code doesn't provide by default.
Better integration with GitHub (GitHub Packages, Actions, etc.)
Better integration with Azure services (e.g. Azure DevOps, Azure Artifacts, etc.)

Feature Planning

Roadmap