[Xquartz-dev] Fully self contained Xquartz.app?

[doh123]

the normal Apple X11 isn't nearly as good.  Just using some from /usr/X11 might work ok, I'm far from an X11 expert.  As far as I know Crossover only uses libXplugin and quartz-wm from Apple's X11, everything else they have in their app.  Their app is portable, because hacked versions of their app made into wrappers can move around everywhere with no issues like i have with xkb, but I'm sure I can figure out a modification to xkb to stop that.

Wine hard compiles the location of X11 dylibs on the system... I want to use something much newer and better than Apple's X11, so for now I compile Wine where X11 is in a non-existant place on other peoples machines, and DYLD_FALLBACK_LIBRARY_PATH is set on run to be the current location it should look for.  I've tried some modifications to use the @exectuable_path... stuff, but theres always been weird issues without having the fallback as well.  Looking close at how Crossover's worked, they are calling the fallback as well, which is how I first found out it existed.  Its difficult trying to make single builds all packaged up that will run on 10.4 - 10.6 correctly without anyone having to custom compile anything.

On Jul 14, 2010, at 1:17 PM, Jeremy Huddleston wrote:

> 
> On Jul 14, 2010, at 09:48, doh123 wrote:
> 
>> because my main goal isn't for Xquartz itself, its for Wineskin, which has Xquartz packaged inside... because Wine has to have X11, and I try to make the apps run as much like a native app as possible, hiding Wine and Xquartz and everything from the user.
> 
> You can require that your users select the X11User.pkg which means they will have /usr/X11 on their system.  This is what Codeweavers does for Crossover currently.
> 
> 
>> Just using the default install of X11 on the system is problematic, since I wouldn't know which features are available from what they had installed,
> 
> what do you mean by that?  It's not like users can configure what parts of X11 they install.  They either have it or they don't.  You get the version that comes with the OS.
> 
>> and that Wine compiles its winex11 driver against the X11 version and location...  
> 
> yeah... and you're building wine, so what's the problem?
> 
> 
> 
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>