{"id":24620,"date":"2019-07-19T22:29:49","date_gmt":"2019-07-19T22:29:49","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=24620"},"modified":"2019-08-15T23:01:27","modified_gmt":"2019-08-15T23:01:27","slug":"vcpkg-2019-06-update","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/vcpkg-2019-06-update\/","title":{"rendered":"Vcpkg: 2019.06 Update"},"content":{"rendered":"

The 2019.06 update of vcpkg, a tool that helps you manage C and C++ libraries on Windows, Linux, and MacOS, is now available. This is the first time we\u2019ve created a vcpkg release on our GitHub repository<\/a>. This update is designed to bring you a summary of the new functionality and improvements made to vcpkg over about a month\u2019s time. The 2019.06 update covers the month of June.<\/p>\n

This release includes many new ports and triplet updates including overlay options, improvements for port contributors, and new documentation. For a full list of this release\u2019s improvements, check out our release notes on GitHub<\/a>.<\/p>\n

Ports<\/h2>\n

There has been a substantial growth in vcpkg contributions over the past few months, with over 1,000 packages now available in the catalog. You can view the libraries available by either searching for a library name in the GitHub repo ports folder<\/a> or using the vcpkg search command<\/a>.<\/p>\n

We added 44 new ports in the month of June. Some notable additions include: bdwgc<\/a>, cJSON<\/a>, greatest<\/a>, immer<\/a>, json-c<\/a>, and zydis<\/a>. These ports have 1K+ stars on their respective GitHub repos. You can view a full list of new ports in the [new ports section of our release notes]().<\/p>\n

In addition to new ports, we updated 291 existing ports. A notable update to the release includes port ‘Homepages’<\/a>.<\/p>\n

Port Homepages<\/h3>\n

As part of our infrastructure work, you can now view the \u2018Homepage\u2019 for a port. This allows you to easily view a port\u2019s official homepage via a link to the website. Let\u2019s take the Abseil port for example. If you navigate to <vcpkg root>\/ports\/abseil\/CONTROL, you will find the line “Homepage: https:\/\/github.com\/abseil\/abseil-cpp<\/a>” which links to the official Abseil page.<\/p>\n

Overlay Ports<\/h2>\n

The vcpkg command line interface allows you to easily search, install, and maintain your libraries. We added an –-overlay-ports<\/code> option to allow you to override ports with alternate versions and create private ports.<\/p>\n

Let\u2019s look at an example where you are using OpenCV for your computer vision project. You would like to use vcpkg to acquire OpenCV and other packages. Your team is specifically using version 3.0 of OpenCV, but vcpkg offers version 3.4.3. Even though that version of OpenCV is not available in vcpkg, you can create a private port.<\/p>\n

Let\u2019s say you go ahead and create a private GitHub repo and check in the ports you want to preserve including OpenCV 3.0 and its specific dependent libraries that also may not be available in current vcpkg. You can then provide your team with the link to clone your private repo.<\/p>\n

Locally, you create a custom ports directory and commit your changes:<\/p>\n

~\/vcpkg$ mkdir vcpkg-custom-ports\r\n~\/vcpkg$ cd vcpkg-custom-ports\r\n~\/vcpkg\/vcpkg-custom-ports$ git init\r\n~\/vcpkg\/vcpkg-custom-ports$ cp -r %VCPKG_ROOT%\/ports\/opencv .\r\n~\/vcpkg\/vcpkg-custom-ports$ git add .\r\n~\/vcpkg\/vcpkg-custom-ports$ git commit -m \"[opencv] Add OpenCV 3.0 port\"\r\n~\/vcpkg\/vcpkg-custom-ports$ git remote add origin https:\/\/github.com\/<My GitHub username>\/vcpkg-custom-ports.git\r\n~\/vcpkg\/vcpkg-custom-ports$ git push -u origin master<\/pre>\n
Now, you and your team can use version 3.0 of OpenCV for your projects with vcpkg using the following:<\/p>\n
~\/vcpkg\/vcpkg-custom-ports$ git clone https:\/\/github.com\/<My GitHub username>\/vcpkg-custom-ports.git\r\n~\/vcpkg\/vcpkg-custom-ports$ .\/vcpkg update --overlay-ports=.\/vcpkg-custom-ports\r\n~\/vcpkg\/vcpkg-custom-ports$ .\/vcpkg upgrade --no-dry-run --overlay-ports=.\/vcpkg-custom-ports<\/pre>\n
Note that you may need to update vcpkg to use the most up-to-date command line options. You can update vcpkg on Windows via .\\bootstrap-vcpkg.bat<\/code> or on macOS \/Linux via .\/bootstrap-vcpkg.sh<\/code>.<\/p>\n
This allows you to upgrade your packages and preserve the older version of OpenCV that your project requires.<\/p>\n
As shown in the example above, you can use\u00a0--overlay-ports<\/code>\u00a0with the\u00a0vcpkg install<\/code>,\u00a0vcpkg update<\/code>,\u00a0vcpkg upgrade<\/code>,\u00a0vcpkg export<\/code>, and\u00a0vcpkg depend-info<\/code>\u00a0commands. Learn more in our overlay-ports documentation<\/a>.<\/p>\n
Note that while overlay ports can help with overriding port versions and creating private ports, this is part of our ongoing work to improve the usability of vcpkg when it comes to versioning. Stay tuned for a future post on best practices for versioning with vcpkg!<\/p>\n
Triplets<\/h2>\n
Vcpkg provides many triplets (target environments) by default. This past month, we focused on increasing the number of ports available on Linux and creating port improvements for Linux and the Windows Subsystem for Linux (WSL). We now have 823 ports available for Linux and we updated over 150 ports for Linux and WSL.<\/p>\n
Here is a current list of ports per triplet:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Triplet<\/td>\nPorts Available<\/td>\n<\/tr>\n
x64-osx<\/td>\n755<\/td>\n<\/tr>\n
x64-linux<\/td>\n823<\/td>\n<\/tr>\n
x64-windows<\/td>\n1006<\/td>\n<\/tr>\n
x86-windows<\/td>\n977<\/td>\n<\/tr>\n
x64-windows-static<\/td>\n895<\/td>\n<\/tr>\n
arm64-windows<\/td>\n654<\/td>\n<\/tr>\n
x64-uwp<\/td>\n532<\/td>\n<\/tr>\n
arm-uwp<\/td>\n504<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Don\u2019t see a triplet you\u2019d like? You can easily add your own triplets. Details on adding triplets can be found in our documentation<\/a>.<\/p>\n
Overlay Triplets<\/h2>\n
As part of our vcpkg command line updates, we also added an --overlay-triplets<\/code> option. This option is especially helpful if you have custom triplet needs. You can use the option, similar to --overlay-ports<\/code>, to override triplets with custom specifications and create custom triplets.<\/p>\n
For example, a subset of Linux users require fully dynamic libraries, whereas the x64-linux triplet only builds static libraries. A custom triplet file based on the x64-linux triplet<\/a> can be created to build dynamic libraries. To solve this problem:<\/p>\n
First, create a folder to contain your custom triplets:<\/p>\n
~\/vcpkg$ mkdir ..\/custom-triplets<\/pre>\n
Then, create the custom triplet file:<\/p>\n
~\/vcpkg$ cp .\/triplets\/x64-linux.cmake ..\/custom-triplets\/x64-linux-dynamic.cmake<\/pre>\n
And modify the custom-triplets\/x64-linux-dynamic.cmake file to:<\/p>\n
set(VCPKG_TARGET_ARCHITECTURE x64) \r\nset(VCPKG_CRT_LINKAGE dynamic) \r\nset(VCPKG_LIBRARY_LINKAGE dynamic) \r\nset(VCPKG_CMAKE_SYSTEM_NAME Linux)<\/pre>\n
* <\/em>Note the change of <\/em>VCPKG_LIBRARY_LINKAGE from static to dynamic.<\/em><\/p>\n
Finally, use your custom triplet by passing the --overlay-triplets<\/code> option:<\/p>\n
~\/vcpkg$ vcpkg install opencv:x64-linux-dynamic --overlay-triplets=..\/custom-triplets<\/pre>\n
Improvements for Port Contributors<\/h2>\n
We also made improvements to the vcpkg infrastructure including a public CI system, check features, and a \u2018Homepage\u2019 field for ports.<\/p>\n
CI System<\/h3>\n
We now have public CI tests through Azure DevOps pipelines which are run for all PRs to the vcpkg GitHub repo. The CI system allows contributors to get direct, automatic access to failure logs for PRs on Linux, Windows, and Mac within minutes. For example:<\/p>\n
\"PR\"GitHub<\/p>\n
The checks will still include badges to indicate pass\/fail as shown by the \u2018x\u2019 or \u2018check mark\u2019.<\/span><\/p>\n
And if a check fails, you can now drill into the details:<\/p>\n
\"PR<\/p>\n
Going further into Azure DevOps, you can get more information in the Summary tab such as downloading a zip file of all the failure logs along with a quick description of relevant changes:<\/p>\n
\"Failed<\/p>\n
We hope the new CI system will improve your experience submitting PRs to vcpkg!<\/p>\n
Check Features<\/h3>\n
Vcpkg_check_features<\/code> is a new portfile function that checks if one or more features are a part of a package installation. In vcpkg we use features to enable optional capabilities offered by libraries. A user requests vcpkg to install. For example:<\/p>\n
~\/vcpkg$ vcpkg install opencv[cuda]<\/pre>\n
The install command enables the optional CUDA support for OpenCV.<\/p>\n
Vcpkg_check_features<\/code>simplifies the portfile creation process for vcpkg contributors by shortening the syntax needed in the CMake portfile script. Previously, you needed to specify which features are included in the port:<\/p>\n
if(<feature> IN_LIST FEATURES)\r\n   set(<var> ON)else()&nbsp;&nbsp; \r\n   set(<var> OFF)\r\nendif()<\/pre>\n
Now, you can simply write the following:<\/p>\n
vcpkg_check_features(<feature> <output_variable>)<\/pre>\n
Learn more about using vcpkg_check_features<\/code> in your portfiles in the vcpkg_check_features<\/code> documentation<\/a>.<\/p>\n
\u2018Homepage\u2019 Field for Ports<\/h3>\n
We also added an optional ‘Homepage’ field to CONTROL. This means that CONTROL files may now contain a ‘Homepage’ field which links to the port’s official website. The Homepage field is designed to help you more easily find the origin\/location of the ports you are using.<\/p>\n
Documentation<\/h2>\n
We also updated our documentation to reflect these new changes. Check out the following new docs for more information on some of the updates outlined in this post in addition to a couple other areas:<\/p>\n