-
Notifications
You must be signed in to change notification settings - Fork 187
Update spdlog to 1.4.2-p2, fixing missing cassert include #111
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
Conversation
All tool-chains that are also run on the 1.4.2-p0 release work. I just did not disable them. But If you insist, I will update the list of tool-chains, and update the PR. |
I’m a bit confused. You mention 1.4.2-p0, but I don’t see that branch or tag anywhere? And then -p1 was a mistake, and -p2 is the new release? Did this ever go through code review? |
|
cmake/projects/spdlog/hunter.cmake
Outdated
VERSION | ||
"1.4.2-p2" | ||
URL | ||
"https://github.com/cpp-pm/spdlog/archive/v1.4.2-p2.tar.gz" |
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 updating of spdlog
's v1.x
branch is confusing. Let's use the convention of last known release version + git hash for the updated version in Hunter. I created the new branch and release for you here: https://github.com/cpp-pm/spdlog/releases/tag/v1.4.2-58e6890-p0 and deleted the other, confusing branches.
For new versions, the branch name should be hunter-<version>
without the p0
. The release+tag adds the p0
, p1
, p2
, etc. so that you can continue patching the same branch but have multiple releases.
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.
you are right, that is much better. Thank you for removing the wrong branches and creating a new one.
I'll update the PR as soon as I find the time for it.
92eed4a
to
7ca4baf
Compare
Removing v prefix on spdlog
7ca4baf
to
c7468d5
Compare
@dan-42 Thanks for updating the PR. Looks like some toolchains failed that weren't before? Can you check them please? |
@rbsheth You're welcome. The toolchains that fail, had been disabled in the last release (1.4.2-p0), see my second comment above. But if you insist I will also disable them just to have passing tests :-) |
@dan-42 Yes, please disable them. :) |
Here are the successful builds: Now shall I provide a PR to |
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.
Yup, a PR to hunter-testing after pkg.template is updated works.
Branch |
PR for hunter-testing: cpp-pm/hunter-testing#32 |
I've followed this guide
step by step carefully. [Yes]
I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":
the -p2 means that I use the latest changes from spdlogs branch
v1.x
which includes a fix when compiling on gcc9.2 which misses an #includePlease delete the following branch
hunter-1.4.2-p1
from the repo https://github.com/cpp-pm/spdlog as I created it accidently from spdlog'smaster
-branch which is wrong.And I do not have the privileges to delete a protected branch.
PING: @bkotzz @rbsheth