Hi Jeremy, Sounds great. Just so I don't do something stupid, could you detail the configure options needed to replicate this setup when building from source (for xserver)? Perhaps an update to the wiki could be in order? :) -- Pelle Johansson 17 sep 2009 kl. 03.47 skrev Jeremy Huddleston:
So, I finally resolved my build issues. Here's 2.4.1_alpha1 for SnowLeopard.
It makes that ptty resize option on by default to workaround the bug in xterm/ptty. It installs in /opt/X11, /Library/Launch*, /Applications/Utilities/ XQuartz.app
This release is the first to allow differnt X11 servers to "own" $DISPLAY. You can pick which X11 server will actually "own" it by disabling the others' startx LaunchAgents. You will notice (after logout/login) that $DISPLAY now has "org.macosforge.xquartz" in its filename which identifies XQuartz.app as the owner.
That being said, SL's X11 assumes that it owns $DISPLAY. If you run X11.app while it's not the owner, it will actually trigger XQuartz.app to start and wait forever for its own startup notification. Hopefully I can get X11 a SoftwareUpdate in a future dot release of OSX to update this (or you can do it on your own by copying over a new X11.bin into X11.app).
X11 servers that don't "own" DISPLAY will unset DISPLAY and their children will continue to use the traditional DISPLAY values (":1", ":2", etc).
I did not update the release notes in the .pkg, so you'll need to check the site for a full changelog:
http://xquartz.macosforge.org/trac/wiki/ChangeLog
Here's the dmg:
http://static.macosforge.org/xquartz/downloads/SL/X11-2.4.1_alpha1.dmg
Note: X11 alpha/beta updates will only be released for SL. rcs will be rolled for both Leo and SL. It's just not worth the extra overhead.
Thanks, Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev