Vcpkg (Install)

Downloads:

49

Downloads of v 2019.06:

49

Maintainer(s):

Software Author(s):

  • Microsoft

Vcpkg (Install)

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

Details

This package was rejected on 18 Jun 2020. The reviewer chocolatey-ops has listed the following reason(s):

Starz0r (maintainer) on 04 Mar 2020 10:24:17 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 04 Mar 2020 10:58:25 +00:00:

vcpkg has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The PackageSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
  • If you are going to use copyright in the nuspec, please use more than 4 characters. More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...

chocolatey-ops (reviewer) on 04 Mar 2020 11:43:39 +00:00:

vcpkg has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/deee81edc66f935613f708dc3c0327bd for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Starz0r (maintainer) on 04 Mar 2020 20:31:06 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 04 Mar 2020 21:05:55 +00:00:

vcpkg has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • If you are going to use copyright in the nuspec, please use more than 4 characters. More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...

chocolatey-ops (reviewer) on 04 Mar 2020 22:03:35 +00:00:

vcpkg has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/d1aa02def39aaa1403cc427b7d879971 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Starz0r (maintainer) on 04 Mar 2020 23:15:03 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 04 Mar 2020 23:47:13 +00:00:

vcpkg has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...

chocolatey-ops (reviewer) on 05 Mar 2020 00:51:30 +00:00:

vcpkg has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/875582a1d50a3c57eb3aa5a5c89bccd1 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Starz0r (maintainer) on 05 Mar 2020 08:15:19 +00:00:

User 'Starz0r' (maintainer) submitted package.

Starz0r (maintainer) on 05 Mar 2020 08:25:22 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Mar 2020 09:01:23 +00:00:

vcpkg has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...

chocolatey-ops (reviewer) on 05 Mar 2020 09:59:15 +00:00:

vcpkg has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/f54f5d6437fb05385624fcc4759bd355 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Starz0r (maintainer) on 05 Mar 2020 11:37:15 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Mar 2020 12:08:32 +00:00:

vcpkg has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...

chocolatey-ops (reviewer) on 05 Mar 2020 13:41:19 +00:00:

vcpkg has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/84fc971aad591379d63cb7f766a21a51 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Starz0r (maintainer) on 05 Mar 2020 22:22:17 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Mar 2020 22:56:19 +00:00:

vcpkg has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...

Starz0r (maintainer) on 05 Mar 2020 23:30:16 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 06 Mar 2020 00:07:00 +00:00:

vcpkg has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...

Starz0r (maintainer) on 06 Mar 2020 01:02:54 +00:00:

Okay it works now, you'll have to exempt the package because it requires Visual Studio to be installed.

chocolatey-ops (reviewer) on 06 Mar 2020 01:23:42 +00:00:

vcpkg has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/8c9eb19709f77d4598fb0cc3ebc40c79 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Starz0r (maintainer) on 06 Mar 2020 06:17:07 +00:00:

Responding so it'll say that I've taken action, read above for my previous response.

flcdrg (reviewer) on 09 Mar 2020 07:11:42 +00:00:

I have some reservations about this package, in the sense that it isn't downloading a binary like most Chocolatey packages, but appears to be cloning the source code and building it locally. I'll get some feedback from the other moderators and get back to you.

David

Starz0r (maintainer) on 09 Mar 2020 09:47:15 +00:00:

It does indeed build a binary. The project does unfortunately put this in a weird position because of how it is setup and requires their to be a "root". They could have done this by just having the tool do this it's self, and not require a clone of the repository, but they do and it's a odd design decision. There is also the fact that they do have Azure CI Pipelines, but they do not include binaries, just logs, so there was no using that site to get a precompiled binary, at all.

So I do understand the reservation on this, and pretty much assumed this would happen. I'll be looking forward to a response in the meanwhile, no pressure.

Pauby (reviewer) on 19 Apr 2020 16:52:05 +00:00:

Hi,

The dependencies in this package just don't look right - can you explain the reason for each one?

Thanks.

Starz0r (maintainer) on 20 Apr 2020 05:10:18 +00:00:

Git is currently required to install vcpkg since it will clone the repository from a specific point in time, however I'm going to change that so it just downloads the ZIP from GitHub and extracts that instead. However Git is still required for other dependencies to be installed from vcpkg, if Git is not detected when vcpkg is ran, it will download a portable version of Git, I feel this is stepping over boundaries, so I require Git to be installed and updated to a specific version up front so it won't try to download a portable version. The portable version is localized to the vcpkg folder anyway, so it won't really mess with anything, but I'd rather it not.

As for Visual Studio, it's required to compile vcpkg since it does not include and pre-compiled binaries, the bootstrapper script will do this. If Visual Studio with the Native Desktop workload is not found the bootstrapper will outright fail, and installation won't continue.

NuGet is also in a similar situation as Git, as it will install a portable version if an update version is not found in PATH. I do this so it can use the system NuGet instead of it's own localized portable version. The same is also true for 7zip, 7zip.portable, and powershell-core.

Pauby (reviewer) on 14 May 2020 10:48:53 +00:00:

Okay. Why is powershell-core a dependency?

chocolatey-ops (reviewer) on 03 Jun 2020 10:49:18 +00:00:

We've found vcpkg v2019.06 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 18 Jun 2020 10:51:45 +00:00:

Unfortunately there has not been progress to move vcpkg v2019.06 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

Vcpkg

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!

Overview

For short description of available commands, run vcpkg help.

Quick Start

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. If your library is not present in vcpkg catalog, you can open an issue on the GitHub repo where the dev team and the community can see it and potentially create the port file for this library.

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


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'SilentlyContinue';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installDir = Join-Path $(Get-ToolsLocation) $PackageName

$preinstalled = Test-Path -Path $installDir -PathType Container
$precompiled = Test-Path -Path "$installDir\vcpkg.exe" -PathType Leaf

if ($preinstalled) {
	Write-Host -ForegroundColor green "Vcpkg repository already exists, pulling new changes instead."
	git pull -C $installDir
} else {
	Write-Host -ForegroundColor green "Cloning GitHub Repository"
	git clone --single-branch --branch 2019.06 https://github.com/Microsoft/vcpkg.git $installDir
}

if ($precompiled) {
	Write-Host -ForegroundColor green "Vcpkg already compiled, deleting executable."
	Remove-Item -Path "$installDir\vcpkg.exe"
}

$ErrorActionPreference = 'Stop';
Write-Host -ForegroundColor green "Bootstraping vcpkg"
Invoke-Expression "$installDir\bootstrap-vcpkg.bat"

Write-Host -ForegroundColor green "Adding Shim to PATH"
Install-BinFile -Name "vcpkg" -Path "$installDir\vcpkg.exe"

Write-Host -ForegroundColor green "Setting vcpkg root"
Invoke-Expression "$installDir\vcpkg.exe integrate install"
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installDir = Join-Path $(Get-ToolsLocation) $PackageName

Uninstall-BinFile -Name "vcpkg" -Path "$installDir\vcpkg.exe"
Remove-Item -Recurse -Force $installDir

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

Discussion for the Vcpkg (Install) Package

Ground Rules:

  • This discussion is only about Vcpkg (Install) and the Vcpkg (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Vcpkg (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus