How do I cause standalone X11 apps to use MacPorts X11?

[Brandon Allbery]

On Wed, Mar 26, 2014 at 12:44 PM, Kevin Reid <kpreid at switchb.org> wrote:

> When I run X11 applications built by MacPorts, they open in the X11 server
> “app” built by MacPorts (/Applications/MacPorts/X11.app). When I run
> separately distributed Mac-packaged X11 applications (MCEdit, Closure (the
> game)), it opens the “X11 is no longer included with OS X” dialog.
>
> How do I get these applications to recognize MacPorts' X11?
>

They're probably linking to stuff under /usr/X11 which is stubbed to
produce that dialog. MacOSForge XQuartz installs a symlink from there to
/opt/X11 to make such things work; a similar symlink to /opt/local might
work (although it is a somewhat unfortunate solution, it seems to be how
Apple expects it to be handled given XQuartz).

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20140326/44b0cb00/attachment.html>