Re: /usr/X11 vs /opt/X11 on Mountain Lion
Re: /usr/X11 vs /opt/X11 on Mountain Lion
- Subject: Re: /usr/X11 vs /opt/X11 on Mountain Lion
- From: Jeremy Huddleston Sequoia <email@hidden>
- Date: Mon, 06 Aug 2012 10:46:48 -0700
On Aug 6, 2012, at 08:38, Tim Jenness <email@hidden> wrote:
> Can someone confirm for me that the only reason I still have a /usr/X11 in
> Mountain Lion is because I updated from Lion? If I did a fresh install of
> Mountain Lion would I only have /opt/X11 from xquartz?
After installing XQuartz on ML, /usr/X11 is a symlink to /opt/X11. This is for compatibility with 3rd party applications that linked against the libraries in /usr/X11. This is the exact same reason why /usr/X11R6 exists as a symlink to /usr/X11 (or now /opt/X11).
> I'm wondering if I should clear out /usr/X11 and /usr/X11R6 so that my
> system acts more like a native Mountain Lion system.
/usr/X11 and /usr/X11R6 are symlinks. You should leave them in place. They'll actually be re-created when you update XQuartz anyways.
> I've already had to go
> through and fix include path issues (I think Lion and Snow Leopard must
> have added /usr/X11/include to compiler search paths automatically) and I
> want to make sure that my new binaries work on clean Mountain Lion Macs.
/usr/X11/include was never in any compiler search path automatically. On previous OS versions, /usr/include/X11 existed as a symlink to /usr/X11/include/X11 for backwards compatability with Tiger's version of X11. That is probably what you are seeing. You should be using pkg-config to determine CFLAGS for the X11 libraries.
Hope that helps,
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden