Conversation
|
the ci says the build fails with libupnp 1.14.18 |
|
Interesting.. Debian/Ubuntu are using a different version scheme for libupnp based on library soname. |
|
For example:
which results in
which results in |
And this is actually a difference between autotools and cmake builds of libupnp. What a mess. =( |
|
So this one is not fixed? |
|
I don't know how to properly fix this for certain libupnp versions built with cmake (including those currently shipped by Debian and Ubuntu). libupnp upstream fixed this at some point, so both cmake and autotools builds now generate consistent version info. E.g. latest 1.18.4 built via cmake has this in the which results in |
|
So we could check and require just a recent enough version. If someone compiles amule, getting a recent libupnp shouldn't be asked too much. |
This has been fixed. The const event thing was my mistake. As a result, some 1.14.x releases have a broken API. My suggestion is to use only the last 1.14.x or 1.18.x. Otherwise you will have to figure out at what point I broke 1.14.x API and ifdef it. Not hard too, but ugly since it is not amule's fault.
Exactly. |
|
I've added a workaround for Debian/Ubuntu and co. Not an elegant solution, but should work. |
Not everyone will like it. And this will break current CI builds. |
|
I broke the 1.14.30 should also compile. |
|
I guess @mrjimenez is the expert here. My solution would be to require 1.18.x on don't work around stuff. Thanks to Christian Marrilat this should be available. |
|
OK. I reverted my patch to the previous version. CI build failure is expected. |
Yes I know this. But this is not the issue. Most distros are likely skipped this release. The issue is that Debian and Ubuntu (at least LTS) are still shipping even older libupnp where pupnp/pupnp#277 is not fixed. |
Fixes #431