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

[stduuid] Update to 1.2.3 #33170

Merged
merged 4 commits into from
Aug 16, 2023
Merged

[stduuid] Update to 1.2.3 #33170

merged 4 commits into from
Aug 16, 2023

Conversation

chausner
Copy link
Contributor

Updates stduuid to 1.2.3

  • Changes comply with the maintainer guide
  • SHA512s are updated for each updated download
  • The "supports" clause reflects platforms that may be fixed by this new version
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

@Adela0814 Adela0814 added the category:port-update The issue is with a library, which is requesting update new revision label Aug 15, 2023
${FEATURE_OPTIONS}
)
vcpkg_cmake_install()

vcpkg_cmake_config_fixup(CONFIG_PATH lib/cmake/${PORT})
file(REMOVE_RECURSE ${CURRENT_PACKAGES_DIR}/lib)
vcpkg_cmake_config_fixup(CONFIG_PATH lib/cmake/stduuid)
Copy link
Contributor

Choose a reason for hiding this comment

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

Please recover to ${PORT}.

Copy link
Contributor Author

@chausner chausner Aug 15, 2023

Choose a reason for hiding this comment

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

In contrast to other paths where we use the "${PORT}" placeholder, this path does not necessarily need to match the port name. It just happens to be identical here. So I thought it's better to be explicit and use "${PORT}" only where where the path really always matches the port name.

Otherwise, it seems pretty arbitrary to me when to use the placeholder and when not. E.g. why don't we use the placeholder here as well, then:

"${CURRENT_PACKAGES_DIR}/include/${PORT}/uuid.h"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed it back to vcpkg_cmake_config_fixup(CONFIG_PATH lib/cmake/${PORT}) in 98af66b.

@Adela0814
Copy link
Contributor

All feature tested pass on the following triplets:

  • x64-windows
  • x64-windows-static
  • x86-windows

Usage tested pass on x64-windows.

@Adela0814
Copy link
Contributor

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

@Adela0814 Adela0814 marked this pull request as draft August 15, 2023 07:34
@chausner chausner marked this pull request as ready for review August 15, 2023 09:47
@Adela0814 Adela0814 added the info:reviewed Pull Request changes follow basic guidelines label Aug 16, 2023
@dan-shaw dan-shaw merged commit 80150f8 into microsoft:master Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-update The issue is with a library, which is requesting update new revision info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants