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
proxy.h breaks when used from C++, and breaks qtbase #226
Comments
But even with this fix, qt5-qtbase doesn't build because the combination of glib and qt headers doesn't work:
|
qy6-qtbase 6.5.0 doesn't build either, I'm not completely sure why, but source file has
|
Interesting, header file name hasn't been changed and you could provide a PR for your second issue. It's valid and should be fixed. Not sure yet about the following ones. @DimStar77 Have you spotted issues on OpenSUSE? |
About the header file: it was in |
Fixes usage of header file from C++. Addresses one part of libproxy#226.
Fixes usage of header file from C++ Addresses one part of #226.
Good catch, yeah. We should fix it as well. |
I don't know my way around meson, sorry. |
I think it would be even better to keep the (new) prefixed location, and simply include that from an unprefixed proxy.h, as that would at least provide the possibility in deprecate the unprefixed location, and drop it in future. |
In this case we can just leave it the way it is, because now or later apps needs to be adjusted... |
Moving the file is a change of the public interface. |
It depends on how much you want to keep strict API compatibility. Anything that uses pkg-config should not have an issue, at least. |
No it is not??? Including it without using pkg-config to find it is a use of the private interface. |
Seems to have fixed it locally, qtbase compilation took a while. Will prepare a PR. |
3rd party libraries (like QT) which defines same variable names will clash if we use gio/gio.h in public proxy.h. Switch to minimal required to fix compilation issues with QT5/6. Fixes: #226
@0-wiz-0 I do have a PR incoming which fixes my local qt6 build. Could you please verify it? |
3rd party libraries (like QT) which defines same variable names will clash if we use gio/gio.h in public proxy.h. Switch to minimal required to fix compilation issues with QT5/6. Fixes: #226
>=libproxy-0.5 moved proxy.h into a non-default include search path. See also: libproxy/libproxy#226 (comment) https://bugs.gentoo.org/906879 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
>=libproxy-0.5 moved proxy.h into a non-default include search path. See also: libproxy/libproxy#226 (comment) https://bugs.gentoo.org/906879 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
>=libproxy-0.5 moved proxy.h into a non-default include search path. See also: libproxy/libproxy#226 (comment) https://bugs.gentoo.org/906879 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
>=libproxy-0.5 moved proxy.h into a non-default include search path. See also: libproxy/libproxy#226 (comment) https://bugs.gentoo.org/906879 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
qt5-qtbase 5.15.9 has two issues with libproxy 0.5
a) it expects to find
libproxy.h
directly in the search path and doesn't seem to use pkg-config to get the proper CFLAGSwhen I work around a) it fails because
b) it tries to use a c++ compiler, and this fails with:
This patch fixes the second problem:
The text was updated successfully, but these errors were encountered: