[MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz
MacPorts
noreply at macports.org
Sat Dec 17 18:35:02 UTC 2022
#66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10:
fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed
for +quartz
-----------------------+----------------------
Reporter: chillin- | Owner: mascguy
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.8.0
Resolution: | Keywords: Mojave
Port: gtk3 |
-----------------------+----------------------
Comment (by kencu):
MacPorts is powerful, and the admins and devs have chosen to keep more
options available at the expense of it being slightly more complicated for
users, especially initially. Homebrew has taken the opposite approach, no
variants, usually one option for things, and they don't support users
building their own software, even.
MacPorts has four xorg-server ports:
{{{
% port search xorg-server
xorg-server @1.20.11_1 (x11, devel)
The X.org / Xquartz X server.
xorg-server-1.18 @1.18.4 (x11, devel)
The X.org / Xquartz X server.
xorg-server-devel @1.20.99.1_1 (x11, devel)
The X.org / Xquartz X server.
xorg-server-legacy @1.20.10_2 (x11, devel)
The X.org / Xquartz X server.
}}}
The primary xorg-server port works for almost all users on newer systems.
The xorg-server-legacy port works on the older systems where the primary
port no longer usually will build or work properly. The other two xorg-
server ports have uses, the 1.18 version on Tiger, and the devel version
for devs to use to move the envelope down the path for the next update.
Now ideally when you tried to install xorg-server on a system that is too
old to support it, it would not tell you it won't build, but try anyway --
that is kinda confusing -- what it would do is say that that xorg-server
doesn't work on your system, so MacPorts will be installing xorg-server-
legacy for you instead. Wouldn't that be great?
It's not overly hard to write that code into the Portfiles, but nobody who
is capable of doing that (like me) has bothered to do it, because there
are just too many other things to do. It would be really great if users
like you might get to the point where you could add that to MacPorts for
us.... we'd really appreciate it.
--
Ticket URL: <https://trac.macports.org/ticket/66476#comment:28>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list