Not sure anyone can assist me with this, but thought it might be worth asking.... hoping someone can point me in the right direction. This is probably something that only effects Macs, since X11 is an extra app, and comes in multiple versions and installed to different locations, and can have more than one on the machine at the same time... When I compile Wine, the X11 driver is hard coded looking for X11 loaded from a specific location... so say my default X11 is in /usr/X11 Wine is built looking for it there. If I have a better/different X11 built in /opt/X11, Wine cannot use it without having to recompile Wine to look for /opt/X11.... it can't change locations. I tried Symlinks hoping it would work, but nothing... This also breaks trying to move the same Wine build from Mac to Mac when X11 is in a different location.... Wine fails because the correct libraries are not listed as being loaded. There has to be a way to get Wine to not look at a hard coded location... I know this since Codeweavers has no problem with their Wine built in Crossover working fine moving its built in X11 anywhere on the machine, and wine still uses it fine. Anyone have any clue where I'd start trying to get it so a single Wine install doesn't have the winex11.drv hard coded to a specific X11 location? or is this a unavoidable limit in Wine that would take source code changes.. that maybe Codeweavers does themselves. I do not mind if it looks for a specific location if it isn't relative to root... like it if always looks in ../../../X11/lib or whatever... or maybe I'm just building Wine wrong somehow and it shouldn't be doing this?
Hi Doh, I dunno if the MacOSX wiki will help: http://wiki.winehq.org/MacOSX If not, have you tried one of the wine/wine-dev ports? MacPorts http://davidbaumgold.com/tutorials/wine-mac/ http://www.macports.org/index.php DarwinPorts: http://wine.darwinports.com/ If you want to compile your own and the MacOSX wiki doesn't help, it might be worth asking on macports/darwinports if they have a forum, aswell, as they clearly specialise in it. Sorry i can't be of any real help, Matthew Millar
>Not sure anyone can assist me with this, but thought it might be worth asking.... hoping someone can point me in the >right direction. >Short answer: LD_LIBRARY_PATH might be the right place to start. There are many problems building Wine on Snow Leopard and that is one of the reasons I have not made the jump, yet. James McKenzie
James Mckenzie wrote:> > > Not sure anyone can assist me with this, but thought it might be worth asking.... hoping someone can point me in the > > right direction. > > > > > Short answer: LD_LIBRARY_PATH might be the right place to start. There are many problems building Wine on Snow Leopard and that is one of the reasons I have not made the jump, yet. > > James McKenzieI have tried LD_LIBRARY_PATH which doesn't seem to do anything on OSX.... I have used the main DYLD functions on OSX... I've tried playing around with.... DYLD_LIBRARY_PATH DYLD_FALLBACK_LIBRARY_PATH DYLD_INSERT_LIBRARIES none seem to help. With DYLD_INSERT_LIBRARIES, i can get past winex11.drv erroring on libX11.6.dylib not being loaded, by inserting the correct(new) path... but then it errors on libSM.6.dylib not loading, and inserting the correct one doesn't seem to help...