C++ Library Manager for Windows, Linux, and MacOS
Go to file
Mark Salisbury 1c2c69529e When downloading a tool, print URL and filepath (#4640)
I'm seeing the error below:

  Building package zlib[core]:x86-windows...
  A suitable version of git was not found (required v2.17.1). Downloading portable git v2.17.1...
  Downloading git...
  WinHttpSendRequest() failed: 12002

I suspect the WinHttpSendRequest error is due to being behind a proxy -
most download issues seem to be this.  Or perhaps because a sys admin
somewhere has disabled WinInet, somehow.  I don't know.  I don't know
how to debug WinHttpSendRequest(); a quick google search didn't help.

By printing the URL that vcpkg is trying to download, and where it's
trying to download to, I can pop the URL in my browser, save it at the
location specified, and move on with my life.
2018-11-02 16:20:02 -07:00
docs xalan-c: Install headers correctly (#4565) 2018-10-25 12:34:45 -07:00
ports [nanodbc] add support for install --head (#4641) 2018-11-02 16:17:07 -07:00
scripts [rocksdb] update to v5.15.10 (#4342) 2018-11-01 20:47:44 -07:00
toolsrc When downloading a tool, print URL and filepath (#4640) 2018-11-02 16:20:02 -07:00
triplets Add triplets for x64-linux and x64-osx 2018-04-23 19:33:19 -07:00
.gitattributes [everything] Use -text to ensure consistent files across machines. 2018-02-26 18:18:05 -08:00
.gitignore [vcxproj] Explicitly specify intermediate and output directories 2018-11-01 01:26:31 -07:00
.vcpkg-root Add .vcpkg-root file that signifies the root directory 2016-09-19 18:49:38 -07:00
bootstrap-vcpkg.bat bootstrap.bat now forwards args to ps1 2018-06-08 16:26:57 -07:00
bootstrap-vcpkg.sh [bootstrap.sh] Fix whitespace-in-path issues 2018-05-16 04:51:08 +00:00
CHANGELOG.md Update CHANGELOG and bump version to 2018.10.20 2018-10-20 17:06:02 -07:00
CONTRIBUTING.md Moved CONTRIBUTING.md to root. Fixes #54. 2016-09-21 13:35:51 -07:00
LICENSE.txt Initial commit 2016-09-18 20:54:03 -07:00
README.md only "optional:" is in italics rather than "optional: CMake 3.10.2" 2018-10-05 12:41:22 +08:00

Vcpkg

Overview

Vcpkg helps you manage C and C++ libraries on Windows, Linux and MacOS. This tool and ecosystem are constantly evolving; your involvement is vital to its success!

For short description of available commands, run vcpkg help.

Quick Start

Prerequisites:

  • Windows 10, 8.1, 7, Linux, or MacOS
  • Visual Studio 2017 or Visual Studio 2015 Update 3 (on Windows)
  • Git
  • Optional: CMake 3.10.2

To get started:

> git clone https://github.com/Microsoft/vcpkg.git
> cd vcpkg

PS> .\bootstrap-vcpkg.bat
Linux:~/$ ./bootstrap-vcpkg.sh

Then, to hook up user-wide integration, run (note: requires admin on first use)

PS> .\vcpkg integrate install
Linux:~/$ ./vcpkg integrate install

Install any packages with

PS> .\vcpkg install sdl2 curl
Linux:~/$ ./vcpkg install sdl2 curl

The best way to use installed libraries with CMake is via the toolchain file scripts\buildsystems\vcpkg.cmake. To use this file, you simply need to add it onto your CMake command line as -DCMAKE_TOOLCHAIN_FILE=[vcpkg root]\scripts\buildsystems\vcpkg.cmake.

In Visual Studio, you can create a New Project (or open an existing one). All installed libraries are immediately ready to be #include'd and used in your project without additional configuration.

For more information, see our using a package example for the specifics.

Additional notes on macOS and Linux support can be found in the official announcement.

Tab-Completion / Auto-Completion

vcpkg supports auto-completion of commands, package names, options etc. To enable tab-completion in Powershell, use

.\vcpkg integrate powershell

and restart Powershell.

Examples

See the documentation for specific walkthroughs, including using a package and adding a new package.

Our docs are now also available online at ReadTheDocs: https://vcpkg.readthedocs.io/!

See a 4 minute video demo.

Contributing

Vcpkg is built with your contributions. Here are some ways you can contribute:

Please refer to our Contribution guidelines for more details.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

License

Code licensed under the MIT License.