-
-
Notifications
You must be signed in to change notification settings - Fork 122
Windows Paths are Returning Backslashes #249
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
Comments
What about the dependant glib/gobject .pc files? |
It looks like gobject-2.0 is returning backslashes as well:
|
I can't reproduce in MSYS2 at least, but we also have some patches. Given the order of the returned paths, maybe have a look at the ffi .pc file? |
Some people want backslashes, others do not. Can we finally make a decision on this. |
afaik backslashes should work fine too, they are just not escaped here. |
I think we should just use forward slashes. If MSYS2 already has a patch for this, I will apply it. |
MSYS2 doesn't have any slash related patches left. My guess would be that there are hardcoded absolute paths in some input .pc files using unescaped backslashes. (sorry that I didn't follow up on Windows issues here... lots of other brokenness in MSYS2 keeping me busy..) |
@lazka including you since you seem to be the pkgconf Windows path guru 👍
A change in gobject-introspection to call
pkg-config.exe --libs-only-L
is causing a gobject-introspection WinError, because the path separators are being stripped out: https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/427With version 1.8.0 and the latest master version built with meson, it is returning backslashes for some of the paths:
Here is the gio-2.0.pc file:
The text was updated successfully, but these errors were encountered: