-
Notifications
You must be signed in to change notification settings - Fork 32
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
[Bug]: warn_unused_result
compilation error in dispenso/priority.cpp
for Linux
#27
Comments
warn_unused_result
` compilation errorwarn_unused_result
compilation error in dispenso/priority.cpp
for Linux
Thanks for the report. I'll try to fix this early next week. |
Hi @RubenRBS Have you tried at main branch instead of release 1.2? I believe this has been addressed. |
Hi @graphicsMan thanks for the suggestion, seems like the current head commit does indeed compile, sorry for the noise! Will there be a tagged release any time soon? I'd much rather merge the Conan recipe once Linux is available so I don't mind waiting :) |
I have a few more minor fixes that can go in too. I'll cut a new release once those are all in, which shouldn't be long. Maybe another week or so. |
Slowly making progress on this. I was out for more than a week with COVID, so please bear with me :) |
Big apologies for this taking so long! Release 1.3 was just cut. Let me know if you run into more issues! |
Hi @graphicsMan thanks a lot for taking the time to address the issue, I appreciate it :) I've now been able to compile in all my supported configurations without issues with the new 1.3 version, so hopefuly conan-io/conan-center-index#22876 gets merged soon 🤞 Thanks a lot for all your support! |
Contact Details
N/A
What happened?
While trying to package the library for Conan Center Index, I've come across a compilation issue due to
warn_unused_result
and the default-Werror
.I'm running
and I'm compiling with
This might be something on my end so sorry about the noise if that's the case, I've tried to check for missconfigurations on my end but I can't see where I would be going wrong :)
Version
1.0 (Default)
Code of Conduct
The text was updated successfully, but these errors were encountered: