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

[rapidcheck] Upgrade to 2023-12-14. #38465

Merged
merged 1 commit into from May 3, 2024

Conversation

yobeonline
Copy link
Contributor

@yobeonline yobeonline commented Apr 29, 2024

Later revisions are available but they introduce pkgconfig support which make vcpkg complain that hard coded file paths are deployed to lib/pkgconfig/*.pc files and I am not sure what to do about them.
Upgraded to the latest revision to date.

  • 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.

@yobeonline
Copy link
Contributor Author

@microsoft-github-policy-service agree

@yobeonline
Copy link
Contributor Author

I have checked the port against g++-13 and VS2022.

@dg0yt
Copy link
Contributor

dg0yt commented Apr 29, 2024

they introduce pkgconfig support which make vcpkg complain that hard coded file paths are deployed to lib/pkgconfig/*.pc files and I am not sure what to do about them.

Call vcpkg_fixup_pkgconfig().

@WangWeiLin-MV WangWeiLin-MV added the category:port-update The issue is with a library, which is requesting update new revision label Apr 30, 2024
@yobeonline yobeonline changed the title [rapidcheck] Upgrade to 2023-08-15. [rapidcheck] Upgrade to 2023-12-14. Apr 30, 2024
@yobeonline
Copy link
Contributor Author

yobeonline commented Apr 30, 2024

Call vcpkg_fixup_pkgconfig().

Done, thanks for your help.

@data-queue data-queue merged commit f32db29 into microsoft:master May 3, 2024
17 checks passed
@yobeonline yobeonline deleted the rapidcheck branch May 3, 2024 07:01
yurybura pushed a commit to yurybura/vcpkg that referenced this pull request May 8, 2024
~~Later revisions are available but they introduce pkgconfig support
which make vcpkg complain that hard coded file paths are deployed to
lib/pkgconfig/*.pc files and I am not sure what to do about them.~~
Upgraded to the latest revision to date.

<!-- If your PR fixes issues, please note that here by adding "Fixes
#NNNNNN." for each fixed issue on separate lines. -->

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

- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [x] SHA512s are updated for each updated download.
- [x] The "supports" clause reflects platforms that may be fixed by this
new version.
- [x] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [x] Any patches that are no longer applied are deleted from the port's
directory.
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants