-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[promise-cpp] Add new port #20340
[promise-cpp] Add new port #20340
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!
PRs must add only one version and must not modify any published versions
When making any changes to a library, the version or port-version in vcpkg.json
or CONTROL
must be modified.
Error: Local changes detected for promise-cpp but no changes to version or port version.
-- Version: 1.0.3
-- Old SHA: fbd1822f72da4ff1934d6395ddd918d68f9c0c0a
-- New SHA: ef3fb5249eed37360ceb9b3b366037ad2ed2c865
-- Did you remember to update the version or port version?
-- Pass `--overwrite-version` to bypass this check.
***No files were updated.***
This is error log: |
I updated the port for the new major version 2.1.0 which was released yesterday. Unfortunately, the CMake install targets have apparently be removed from CMakeLists.txt so I now simply copy the headers into The suggestion by vcpkg is not ideal, though:
|
Add a |
Thanks, added a usage file. |
I'm concerned that this port takes likely to conflict names:
Would you consider it acceptable to install into a subidrectory like |
I noticed there is also another issue that is preventing the port from being usable right now: https://github.com/xhawk18/promise-cpp/blob/5e533a1c2beb363ca6b87f7f002007388349366c/include/promise.hpp#L262 I will open an issue and ask the maintainer if they can address these issues in the library itself so we don't have to work around them with patches. |
Ouch! Best of luck! |
@BillyONeal This should be ready now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for your contribution!
Thanks for running that down with upstream! |
Describe the pull request
What does your PR fix?
Adds new port promise-cpp
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