Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update ned14-internal-quickcpplib, status_code, outcome and llfio to latest #21926

Merged
merged 1 commit into from
Dec 8, 2021

Conversation

ned14
Copy link
Contributor

@ned14 ned14 commented Dec 8, 2021

Describe the pull request

Update ned14-internal-quickcpplib, status_code, outcome and llfio to latest.

Yes

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

Yes

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You have modified or added at least one portfile where deprecated functions are used.

If you feel able to do so, please consider migrating them to the new functions:
vcpkg_install_cmake -> vcpkg_cmake_install (from port vcpkg-cmake)
vcpkg_build_cmake -> vcpkg_cmake_build (from port vcpkg-cmake)
vcpkg_configure_cmake -> vcpkg_cmake_configure (Please remove the option PREFER_NINJA) (from port vcpkg-cmake)
vcpkg_fixup_cmake_targets -> vcpkg_cmake_config_fixup (from port vcpkg-cmake-config)

In the ports that use the new function, you have to add the corresponding dependencies:

{
  "name": "vcpkg-cmake",
  "host": true
},
{
  "name": "vcpkg-cmake-config",
  "host": true
}

The following files are affected:

  • ports/llfio/portfile.cmake
  • ports/outcome/portfile.cmake
  • ports/status-code/portfile.cmake

@ras0219-msft
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ras0219-msft ras0219-msft merged commit 6386c01 into microsoft:master Dec 8, 2021
@ras0219-msft
Copy link
Contributor

Thanks for sending us a PR for the updates!

@ned14
Copy link
Contributor Author

ned14 commented Dec 9, 2021

You're welcome! I think that was the most troublefree update I've submitted yet, so my thanks to you and your team!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants