C++ Library Manager for Windows, Linux, and MacOS

Overview

Vcpkg: Overview

中文总览 Español 한국어 Français

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.

For short description of available commands, once you've installed vcpkg, you can run vcpkg help, or vcpkg help [command] for command-specific help.

Build Status

Table of Contents

Getting Started

First, follow the quick start guide for either Windows, or macOS and Linux, depending on what you're using.

For more information, see Installing and Using Packages. If a library you need is not present in the vcpkg catalog, you can open an issue on the GitHub repo where the vcpkg team and community can see it, and potentially add the port to vcpkg.

After you've gotten vcpkg installed and working, you may wish to add tab completion to your shell.

Finally, if you're interested in the future of vcpkg, check out the manifest guide! This is an experimental feature and will likely have bugs, so try it out and open all the issues!

Quick Start: Windows

Prerequisites:

  • Windows 7 or newer
  • Git
  • Visual Studio 2015 Update 3 or greater with the English language pack

First, download and bootstrap vcpkg itself; it can be installed anywhere, but generally we recommend using vcpkg as a submodule for CMake projects, and installing it globally for Visual Studio projects. We recommend somewhere like C:\src\vcpkg or C:\dev\vcpkg, since otherwise you may run into path issues for some port build systems.

> git clone https://github.com/microsoft/vcpkg
> .\vcpkg\bootstrap-vcpkg.bat

To install the libraries for your project, run:

> .\vcpkg\vcpkg install [packages to install]

You can also search for the libraries you need with the search subcommand:

> .\vcpkg\vcpkg search [search term]

In order to use vcpkg with Visual Studio, run the following command (may require administrator elevation):

> .\vcpkg\vcpkg integrate install

After this, you can now create a New non-CMake Project (or open an existing one). All installed libraries are immediately ready to be #include'd and used in your project without additional configuration.

If you're using CMake with Visual Studio, continue here.

In order to use vcpkg with CMake outside of an IDE, you can use the toolchain file:

> cmake -B [build directory] -S . -DCMAKE_TOOLCHAIN_FILE=[path to vcpkg]/scripts/buildsystems/vcpkg.cmake
> cmake --build [build directory]

With CMake, you will still need to find_package and the like to use the libraries. Check out the CMake section for more information, including on using CMake with an IDE.

For any other tools, including Visual Studio Code, check out the integration guide.

Quick Start: Unix

Prerequisites for Linux:

Prerequisites for macOS:

First, download and bootstrap vcpkg itself; it can be installed anywhere, but generally we recommend using vcpkg as a submodule for CMake projects.

$ git clone https://github.com/microsoft/vcpkg
$ ./vcpkg/bootstrap-vcpkg.sh

To install the libraries for your project, run:

$ ./vcpkg/vcpkg install [packages to install]

You can also search for the libraries you need with the search subcommand:

$ ./vcpkg/vcpkg search [search term]

In order to use vcpkg with CMake, you can use the toolchain file:

$ cmake -B [build directory] -S . -DCMAKE_TOOLCHAIN_FILE=[path to vcpkg]/scripts/buildsystems/vcpkg.cmake
$ cmake --build [build directory]

With CMake, you will still need to find_package and the like to use the libraries. Check out the CMake section for more information on how best to use vcpkg with CMake, and CMake Tools for VSCode.

For any other tools, check out the integration guide.

Installing Linux Developer Tools

Across the different distros of Linux, there are different packages you'll need to install:

  • Debian, Ubuntu, popOS, and other Debian-based distributions:
$ sudo apt-get update
$ sudo apt-get install build-essential tar curl zip unzip
  • CentOS
$ sudo yum install centos-release-scl
$ sudo yum install devtoolset-7
$ scl enable devtoolset-7 bash

For any other distributions, make sure you're installing g++ 6 or above. If you want to add instructions for your specific distro, please open a PR!

Installing macOS Developer Tools

On macOS 10.15, the only thing you should need to do is run the following in your terminal:

$ xcode-select --install

Then follow along with the prompts in the windows that comes up.

On macOS 10.14 and previous, you'll also need to install g++ from homebrew; follow the instructions in the following section.

Installing GCC for macOS before 10.15

This will only be necessary if you're using a macOS version from before 10.15. Installing homebrew should be very easy; check out <brew.sh> for more information, but at its simplest, run the following command:

$ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

Then, in order to grab an up-to-date version of gcc, run the following:

$ brew install gcc

You'll then be able to bootstrap vcpkg along with the quick start guide

Using vcpkg with CMake

If you're using vcpkg with CMake, the following may help!

Visual Studio Code with CMake Tools

Adding the following to your workspace settings.json will make CMake Tools automatically use vcpkg for libraries:

{
  "cmake.configureSettings": {
    "CMAKE_TOOLCHAIN_FILE": "[vcpkg root]/scripts/buildsystems/vcpkg.cmake"
  }
}

Vcpkg with Visual Studio CMake Projects

Open the CMake Settings Editor, and under CMake toolchain file, add the path to the vcpkg toolchain file:

[vcpkg root]/scripts/buildsystems/vcpkg.cmake

Vcpkg with CLion

Open the Toolchains settings (File > Settings on Windows and Linux, CLion > Preferences on macOS), and go to the CMake settings (Build, Execution, Deployment > CMake). Finally, in CMake options, add the following line:

-DCMAKE_TOOLCHAIN_FILE=[vcpkg root]/scripts/buildsystems/vcpkg.cmake

Unfortunately, you'll have to add this to each profile.

Vcpkg as a Submodule

When using vcpkg as a submodule of your project, you can add the following to your CMakeLists.txt before the first project() call, instead of passing CMAKE_TOOLCHAIN_FILE to the cmake invocation.

set(CMAKE_TOOLCHAIN_FILE ${CMAKE_CURRENT_SOURCE_DIR}/vcpkg/scripts/buildsystems/vcpkg.cmake
  CACHE STRING "Vcpkg toolchain file")

This will still allow people to not use vcpkg, by passing the CMAKE_TOOLCHAIN_FILE directly, but it will make the configure-build step slightly easier.

Tab-Completion/Auto-Completion

vcpkg supports auto-completion of commands, package names, and options in both powershell and bash. To enable tab-completion in the shell of your choice, run:

> .\vcpkg integrate powershell

or

$ ./vcpkg integrate bash

depending on the shell you use, then restart your console.

Examples

See the documentation for specific walkthroughs, including installing and using a package, adding a new package from a zipfile, and adding a new package from a GitHub repo.

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

See a 4 minute video demo.

Contributing

Vcpkg is an open source project, and is thus built with your contributions. Here are some ways you can contribute:

Please refer to our Contributing Guide for more details.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or email [email protected] with any additional questions or comments.

License

The code in this repository is licensed under the MIT License.

Telemetry

vcpkg collects usage data in order to help us improve your experience. The data collected by Microsoft is anonymous. You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics, passing --disable-metrics to vcpkg on the command line, or by setting the VCPKG_DISABLE_METRICS environment variable.

Read more about vcpkg telemetry at docs/about/privacy.md

Comments
  • [new port] gtk 3.24.34 port

    [new port] gtk 3.24.34 port

    New port: gtk 3.24.34 (some software still requires GTK3)

    • What does your PR fix?

    • Which triplets are supported/not supported? Have you updated the CI baseline?

    all

    Yes

    • If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

    Yes

    If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

    category:new-port depends:different-pr 
    opened by mkhon 131
  • [wxwidgets] Fix usage, add cmake options

    [wxwidgets] Fix usage, add cmake options

    This PR will:

    • Automatically call wx-config and parse out cxxflags in vcpkg-cmake-wrapper.
    • Export all targets.
    • Fix the ouput path by running wx-config --libs.

    Fixes #17072.

    Upstream PR: https://github.com/wxWidgets/wxWidgets/pull/2391

    category:port-bug info:internal depends:upstream-changes 
    opened by JackBoosY 128
  • [OpenCV] Update to v4.1.1

    [OpenCV] Update to v4.1.1

    Any feedback is welcome!

    fixes: #2065 fixes: #2749 fixes: #2799 fixes: #3095 fixes: #3418 fixes: #4160 fixes: #4601 fixes: #4725 fixes: #4758 fixes: #5101 fixes: #5557 fixes: #5876 fixes: #6728 fixes: #6994

    opened by cenit 121
  • [opencv4] update to v4.3

    [opencv4] update to v4.3

    It should be complete now

    Fixes: #11557 Closes: #8557 Fixes: #11138 Fixes: #10188 Closes: #8655 Closes: #8549 Closes: #3196 Fixes: #7981 Closes: #7913 Closes: #7856 Fixes: #4907 Closes: #9607 Fixes: #7572 Closes: #8175

    category:port-update info:reviewed 
    opened by cenit 111
  • More or less completely rewritten tensorflow-cc port

    More or less completely rewritten tensorflow-cc port

    • fixes static builds
    • upgrades tensorflow from v1.14 to recent v2.3, fixing #9141
    • upgrades bazel from v0.25.2 to v3.1, hopefully fixing #7995
    • requires PR #12926 (merged in this branch; need to resolve conflict once PR #12926 is merged into master)
    category:port-feature category:port-update category:tool-update 
    opened by jgehw 103
  • [OpenMVG/OpenMVS] fix tools

    [OpenMVG/OpenMVS] fix tools

    Upgrade SuiteSparse, add new vlfeat port, restore the custom FindLAPACK (for clapack) I wrote one year ago that went lost (and with it each and every port depending on clapack was broken again on linux), remove the unnecessary FindBLAS module, and finally

    • add openMVG tools
    • fix openMVG build error
    • enable cuda on openMVS
    • handle openMVS tools properly

    along the way, it fixes: #12387 (a working qt5 was necessary to build tools cited above) and fixes many problems encountered along the way towards a working solution

    category:port-feature category:port-bug info:reviewed 
    opened by cenit 92
  • [Qt6|6.1.0] Add new ports.

    [Qt6|6.1.0] Add new ports.

    closes #15029

    Current Status:

    • added all 6.1.0 ports which I know of (does it work? Who knows?)

    Current questions:

    • Port naming? qt6-qtbase? Only qtbase? (since qt wants to get rid of the version number anyway)
    • Features? Too many? Will never be all tested. (at least I will only be going for the default set.)

    Depends:

    • [x] #14308
    • [x] #14395 (ZSTD)
    • [x] #14530 (harfbuzz)
    • [x] another PR copying pdbs for vcpkg_copy_tools
    • [x] https://bugreports.qt.io/browse/QTBUG-88457 (qtdeclarative x64-windows-static; not in beta5; probably in beta6)
    • [x] open upstream issues
    • [x] https://bugreports.qt.io/browse/QTBUG-89204 (solved by own patch)
    • [x] https://bugreports.qt.io/browse/QTBUG-89203 (solved by own patch)
    • [x] https://bugreports.qt.io/browse/QTBUG-89280 (solved by own patch)
    • [x] https://bugreports.qt.io/browse/QTBUG-89374 (solved by own patch)
    • [x] fix import prefix correction in vcpkg_fixup_cmake_targets as mentioned in https://github.com/microsoft/vcpkg/pull/12215#discussion_r454579077. (Corrected it in another way for this PR)
    • [x] #15049
    • [x] #15144
    category:new-port info:reviewed 
    opened by Neumann-A 89
  • [openssl] update to 3.0.2

    [openssl] update to 3.0.2

    Describe the pull request This PR updates openssl to version 3.0.2. ~~The consensus is to update openssl and to create a new port called openssl1 for future updates to openssl 1.1.1. No port depends or should ever depend on openssl1. All ports that were incompatible to OpenSSL 3 were updated or patched.~~

    See below.

    • What does your PR fix?

      Fixes #20031

    • Which triplets are supported/not supported? Have you updated the CI baseline?

      ~~Yes, skip openssl1 on all triplets~~

    • Does your PR follow the maintainer guide?

      Yes

    • If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

      Yes

    category:port-update info:reviewed 
    opened by Thomas1664 87
  • [eigen3] Update to 3.4.0

    [eigen3] Update to 3.4.0

    Describe the pull request

    • What does your PR fix?

      Updates Eigen to 3.4.0

    • Which triplets are supported/not supported? Have you updated the [CI baseline]

      all

    • Does your PR follow the [maintainer guide]

      Yes

    • If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

      Yes

    I think this is good to go but have opened it as a draft as it is my first time.

    category:port-update info:reviewed 
    opened by spinicist 83
  • [new port] at-spi2-atk 2.38.0 port

    [new port] at-spi2-atk 2.38.0 port

    at-spi2-atk 2.38.0 port at-spi2-core 2.44.1 port

    Describe the pull request

    • What does your PR fix?

    The port provides at-spi2-atk dependency needed by gtk3

    • Which triplets are supported/not supported? Have you updated the CI baseline?

    linux

    Yes

    • If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

    Yes

    If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

    category:new-port depends:vm-update 
    opened by mkhon 79
  • [android] vcpkg_configure_make correct set flags for android build

    [android] vcpkg_configure_make correct set flags for android build

    vcpkg_configure_make properly set CFLAGS, CXXFLAGS, LDFLAG, CC and CXX env variables now for android cross compilation.

    • Which triplets are supported/not supported? Mostly android triplets,

    • Have you updated the CI baseline? - no

    • Does your PR follow the maintainer guide? yes

    category:tool-update 
    opened by xandox 79
  • [pangolin] Fix regressions

    [pangolin] Fix regressions

    • What does your PR fix?

      Fixes a baseline regression due to conflict caused by vendored copy of palsigslot. Fixes a regression in fixup of absolute paths. Rectifies the usage doc.
    opened by dg0yt 0
  • [lapack-reference] Update, fixes

    [lapack-reference] Update, fixes

    • What does your PR fix?

      Updates to 3.11.0. Fixes release-only lib reference in exported config (for #21415). Fixes uncontrolled usage of external blas. Fixes broken usage output from vcpkg tool heuristics. Enables find_package(LAPACK) test in CI test port.
    opened by dg0yt 0
  • [boost-regex, boost-system] build failure on x64-windows, arm64-windows

    [boost-regex, boost-system] build failure on x64-windows, arm64-windows

    Host Environment

    • OS: Windows
    • Compiler: VC17

    To Reproduce

    Steps to reproduce the behavior:

    ./vcpkg install boost-regex:x64-windows ./vcpkg install boost-regex:arm64-windows

    I see the same behavior on other boost packages that require compilation, e.g. boost-system

    Failure logs

    Console:

    C:\Git\openscad>vcpkg install boost-regex:arm64-windows
    Computing installation plan...
    The following packages will be built and installed:
        boost-regex[core]:arm64-windows -> 1.81.0
    Detecting compiler hash for triplet arm64-windows...
    Restored 0 package(s) from C:\Users\steph\AppData\Local\vcpkg\archives in 128.3 us. Use --debug to see more details.
    Installing 1/1 boost-regex:arm64-windows...
    Building boost-regex[core]:arm64-windows...
    -- Using cached boostorg-regex-boost-1.81.0.tar.gz.
    -- Cleaning sources at C:/Git/vcpkg/buildtrees/boost-regex/src/ost-1.81.0-5d02094f20.clean. Use --editable to skip cleaning for the packages you specify.
    -- Extracting source C:/Git/vcpkg/downloads/boostorg-regex-boost-1.81.0.tar.gz
    -- Using source at C:/Git/vcpkg/buildtrees/boost-regex/src/ost-1.81.0-5d02094f20.clean
    -- Including C:/Git/vcpkg/ports/boost-regex/b2-options.cmake
    -- Found external ninja('1.11.0').
    -- Getting CMake variables for arm64-windows
    -- Configuring arm64-windows
    -- Building arm64-windows-dbg
    CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:131 (message):
        Command failed: C:/Git/vcpkg/downloads/tools/cmake-3.25.0-windows/cmake-3.25.0-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j9
        Working Directory: C:/Git/vcpkg/buildtrees/boost-regex/arm64-windows-dbg
        See logs for more information:
          C:\Git\vcpkg\buildtrees\boost-regex\install-arm64-windows-dbg-out.log
    
    Call Stack (most recent call first):
      installed/arm64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
      installed/arm64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
      installed/arm64-windows/share/boost-build/boost-modular-build.cmake:137 (vcpkg_cmake_install)
      ports/boost-regex/portfile.cmake:12 (boost_modular_build)
      scripts/ports.cmake:147 (include)
    
    
    error: building boost-regex:arm64-windows failed with: BUILD_FAILED
    error: Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
    Then check for known issues at:
        https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-regex
    You can submit a new issue at:
        https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[boost-regex]+Build+error
    Include '[boost-regex] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
        vcpkg-tool version: 2022-12-14-7ae0d8527fb488fde10a89c2813802dc9b03b6f9
        vcpkg-scripts version: f9bea5d58 2022-12-31 (2 days ago)
    

    install-arm64-windows-dbg-out

    [1/2] cmd.exe /C "cd /D C:\Git\vcpkg\buildtrees\boost-regex\src\ost-1.81.0-5d02094f20.clean\build && C:\Git\vcpkg\installed\arm64-windows\tools\boost-build\b2.exe toolset=msvc --user-config=C:/Git/vcpkg/buildtrees/boost-regex/x64-windows-dbg/user-config.jam --stagedir=C:/Git/vcpkg/buildtrees/boost-regex/x64-windows-dbg/stage --build-dir=C:/Git/vcpkg/buildtrees/boost-regex/x64-windows-dbg runtime-link=shared link=shared address-model=64 architecture=x86 target-os=windows threadapi=win32 variant=debug --disable-icu --disable-icu --with-atomic --with-random --with-date_time --with-filesystem --with-system --with-thread --with-chrono -j 9 -sBOOST_ROOT=C:/Git/vcpkg/installed/arm64-windows/tools/boost-build -sBOOST_BUILD_PATH=C:/Git/vcpkg/installed/arm64-windows/tools/boost-build --debug-configuration --debug-building --debug-generators --ignore-site-config --hash -q debug-symbols=on -d +2 threading=multi stage"
    FAILED: CMakeFiles/boost C:/Git/vcpkg/buildtrees/boost-regex/x64-windows-dbg/CMakeFiles/boost 
    cmd.exe /C "cd /D C:\Git\vcpkg\buildtrees\boost-regex\src\ost-1.81.0-5d02094f20.clean\build && C:\Git\vcpkg\installed\arm64-windows\tools\boost-build\b2.exe toolset=msvc --user-config=C:/Git/vcpkg/buildtrees/boost-regex/x64-windows-dbg/user-config.jam --stagedir=C:/Git/vcpkg/buildtrees/boost-regex/x64-windows-dbg/stage --build-dir=C:/Git/vcpkg/buildtrees/boost-regex/x64-windows-dbg runtime-link=shared link=shared address-model=64 architecture=x86 target-os=windows threadapi=win32 variant=debug --disable-icu --disable-icu --with-atomic --with-random --with-date_time --with-filesystem --with-system --with-thread --with-chrono -j 9 -sBOOST_ROOT=C:/Git/vcpkg/installed/arm64-windows/tools/boost-build -sBOOST_BUILD_PATH=C:/Git/vcpkg/installed/arm64-windows/tools/boost-build --debug-configuration --debug-building --debug-generators --ignore-site-config --hash -q debug-symbols=on -d +2 threading=multi stage"
    notice: loading B2 from C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/kernel/bootstrap.jam
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/util\numbers.jam:23: in check from module numbers
    error: 64 in 64 1024 64
    error: is not a number
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/util\numbers.jam:50: in numbers.range from module numbers
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/tools/features\cxx-template-depth-feature.jam:33: in load from module cxx-template-depth-feature
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/kernel\modules.jam:294: in import from module modules
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/tools/features\__init_features__.jam:22: in load from module __init_features__
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/kernel\modules.jam:294: in import from module modules
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/tools\builtin.jam:16: in load from module builtin
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/kernel\modules.jam:294: in import from module modules
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src\build-system.jam:12: in load from module build-system
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/kernel\modules.jam:294: in import from module modules
    C:/Git/vcpkg/installed/arm64-windows/tools/boost-build/src/kernel/bootstrap.jam:135: in module scope from module
    
    ninja: build stopped: subcommand failed.
    

    Additional context

    My guess is that there's a missing compiler setting in msvc.jam, but I don't understand this well enough to try fixing it myself.

    category:port-bug 
    opened by stephenjust 0
  • Upgrading dataframe to version 1.22.0

    Upgrading dataframe to version 1.22.0

    Describe the pull request

    • What does your PR fix?

      It is an upgrade of dataframe package to version 1.22.0

    • Which triplets are supported/not supported? Have you updated the CI baseline?

      all, Yes

    • Does your PR follow the maintainer guide?

      Yes

    • If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

      <Yes / I am still working on this PR>

    If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

    opened by hosseinmoein 2
  • [7zip] Build error

    [7zip] Build error

    Package: 7zip[core]:x86-windows -> 22.01

    Host Environment

    • Host: x86-windows
    • Compiler: MSVC 19.16.27048.0
    • vcpkg-tool version: 2022-12-14-7ae0d8527fb488fde10a89c2813802dc9b03b6f9 vcpkg-scripts version: f9bea5d58 2022-12-31 (2 days ago)

    To Reproduce

    vcpkg install 7zip

    Failure logs

    -- Downloading https://www.7-zip.org/a/7z2201-src.7z -> 7z2201-src.7z...
    -- Extracting source C:/Dev/vcpkg/downloads/7z2201-src.7z
    -- Using source at C:/Dev/vcpkg/buildtrees/7zip/src/7z2201-src-29a5a1119a.clean
    -- Configuring x86-windows
    CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:96 (message):
        Command failed: "C:/Program Files/Microsoft Visual Studio/2017/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
        Working Directory: C:/Dev/vcpkg/buildtrees/7zip/x86-windows-rel/vcpkg-parallel-configure
        Error code: This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher
        See logs for more information:
    
    Call Stack (most recent call first):
      installed/x86-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:247 (vcpkg_execute_required_process)
      ports/7zip/portfile.cmake:17 (vcpkg_cmake_configure)
      scripts/ports.cmake:147 (include)
    
    
    
    

    Additional context

    2nd try with vcpkg (zlib and 7zip). Not much luck.

    category:port-bug 
    opened by kdadmin 0
Releases(2022.11.14)
Owner
Microsoft
Open source projects and samples from Microsoft
Microsoft
CMake wrapper for Xrepo C and C++ package manager

xrepo-cmake CMake wrapper for Xrepo C and C++ package manager. Supporting the project Support this project by becoming a sponsor. Your logo will show

xmake-io 23 Nov 29, 2022
CMake scripts for painless usage of SuiteSparse+METIS from Visual Studio and the rest of Windows/Linux/OSX IDEs supported by CMake

CMake scripts for painless usage of Tim Davis' SuiteSparse (CHOLMOD,UMFPACK,AMD,LDL,SPQR,...) and METIS from Visual Studio and the rest of Windows/Lin

Jose Luis Blanco-Claraco 395 Dec 24, 2022
C package manager-ish

clib(1) Package manager for the C programming language. Installation Expects libcurl to be installed and linkable. With homebrew: $ brew install clib

clibs 4.5k Jan 6, 2023
C++ Package Manager

CPM Note CPM is not being actively maintained. I plan on keeping the website active but don't plan on making further modifications to the codebase. If

James 720 Dec 18, 2022
A CMake toolchain file for iOS, macOS, watchOS & tvOS C/C++/Obj-C++ development

A CMake toolchain file for iOS, macOS, watchOS & tvOS C/C++/Obj-C++ development

Alexander Widerberg 1.4k Jan 4, 2023
📦 CMake's missing package manager. A small CMake script for setup-free, cross-platform, reproducible dependency management.

Setup-free CMake dependency management CPM.cmake is a CMake script that adds dependency management capabilities to CMake. It's built as a thin wrapper

CPM.cmake 1.6k Jan 9, 2023
Enhanced CMake Project Manager plugin for Qt Creator

CMakeProjectManager2 Alternative CMake support for Qt Creator. Main differents from original CMakeProject plugin: Project file list readed from file s

Alexander Drozdov 71 Nov 20, 2022
New gen. Linux

ExtremeCodeOS New gen. Linux Преамбула Необходимо исправить все недостатки линукса и сделать самый лучший и самый доступный дистрибутив из всех сущест

Artem Dontsov 302 Dec 20, 2022
Installation example for a C++ project (Windows) with Cmake.

CMakeInstallExample Installation example for a C++ project (Windows) with Cmake. Contents This project demonstrates how to use cmake with cpack to gen

Paul T 30 Jan 3, 2023
CMake module for building Windows Installer packages with WiX toolset

FindWiX CMake module for building Windows Installer packages with WiX toolset Introduction Requirements Usage find_package() wix_add_project() WiX com

Apriorit Inc. 11 Aug 5, 2022
Example library that shows best practices and proper usage of CMake by using targets

Modern CMake Sample Sample project that shows proper modern CMake usage on a dummy library and an executable that uses it. Accompanying code to my blo

Pablo Arias 601 Dec 29, 2022
Utility and common library for all polysquare cmake tools.

Polysquare CMake Tooling Utility Functions Utility and common library for all polysquare cmake tools. Status Travis CI (Ubuntu) AppVeyor (Windows) Cov

ポリ平方 POLYSQUARE 3 May 7, 2021
nabs is a single-header library for writing build recipes in C++

nabs is a single-header library for writing build recipes in C++. It is directly inspired by nobuild, but with more feature (bloat) and built-in support for makefile-like dependency resolution.

zhiayang 6 May 8, 2021
a lua extend library

colib 这是一个Lua扩展库,提供了一些常用的扩展功能,该库还在不断完善中。。。 功能列表 已提供的模块有: rtl模块: 提供基础的面向对象实现。 dbg模块: 扩展的traceback函数,可以打印每一调用层级的变量值。 打印Lua对象为字符串形式。 高精度时钟 list对象: 数组对象,接

colin 39 Dec 17, 2022
Simple library for embedding static resources into C++ binaries using CMake

libromfs libromfs is an easy way to bundle resources directly into any C++ application and access them through a simple interface. The main advantage

WerWolv 28 Nov 30, 2022
An OS-agnostic C++ library template in plain CMake.

?? How to export C++ library This repository provides an OS-agnostic C++ library template with plain CMake files with the following features: distribu

Robotology 302 Dec 17, 2022
A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.

Buck Buck is a build tool. To see what Buck can do for you, check out the documentation at http://buck.build/. Installation Since Buck is used to buil

Facebook 8.5k Jan 7, 2023
Tundra is a code build system that tries to be accurate and fast for incremental builds

Tundra, a build system Tundra is a high-performance code build system designed to give the best possible incremental build times even for very large s

Andreas Fredriksson 400 Dec 23, 2022
Yet another post-build step and class to bring reflection to C++ enumerations.

enum_values Yet another post-build step and class to bring reflection to C++ enumerations! Fair warning: this project has not undergone much testing (

null 12 May 11, 2022