-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
libvault/0.51.0 #14234
libvault/0.51.0 #14234
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
f91dde9
to
281c913
Compare
This comment has been minimized.
This comment has been minimized.
e4354ed
to
c074eea
Compare
This comment has been minimized.
This comment has been minimized.
The failure in CI system is unexpected, I've tested it on MacOS and Linux without issues. Unfortunately it's opaque as I can't gain access to the build output to see what has failed. |
Because there is a CI failure saying that the current version is `1.53.0`, despite `1.54.0` being available, I've knocked this value down.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hooks produced the following warnings for commit b5f316dlibvault/0.48.0
libvault/0.51.0
|
@uilianries and @SSE4, I was wondering if you would mind providing a review, please - you both approved the original inclusion back in #9117. I've spent a fair bit of time tidying this up to meet all the current standards. |
self.cpp_info.libs = tools.collect_libs(self) | ||
self.cpp_info.libs = collect_libs(self) | ||
if self.settings.compiler == "gcc" and Version(self.settings.compiler.version).major == "8": | ||
self.cpp_info.system_libs.append("stdc++fs") |
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.
I have to say, this workaround to make the test package compile for GCC 8 was a bit of a stumper for a while; I'm not sure if there is any detection that can be done around this in the report back to the recipe developer from the CI system.
For reference, it would manifest as:
.../lib/libvault.so: undefined reference to `std::filesystem::__cxx11::path::_M_split_cmpts()'
collect2: error: ld returned 1 exit status
@sonicxml FYI, I'm updating your original recipe if you'd like to review this update. |
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.
@goodtune Thank you for your contribution. Please, take a look on the review.
Thanks @uilianries I will make those recommended updates and push later today. |
This comment has been minimized.
This comment has been minimized.
1a1ffc1
to
ad1906b
Compare
This comment has been minimized.
This comment has been minimized.
Hooks produced the following warnings for commit ad1906blibvault/0.48.0
libvault/0.51.0
|
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
Specify library name and version: libvault/0.51.0
This is just an update to an existing package to provide the latest version on CCI.