Need help editing wine.

[sonicfan1012]

I need to know how to edit wine so that it uses an application of another name rather than X11. The application of a different name is the same as X11, just a different name. But it's only the application. I have all the X11 files. I just need the name of the APPLICATION that it uses to not be X11 and to be another name.
Please don't think too hard about why I'm using an application with a different name that's the same as X11, you'll probly end up confusin urself just tell me how to change it so that wine will use an APPLICATION with a different name than X11.

[vitamin]

I need to know how to edit wine so that it uses an application of another name rather than X11.

You'll have to change Wine's source code to look for a different library.

[doh123]

Your question doesn't make much sense.

What OS are you running on?

Wine compiles against the X you want to compile agasint in the location you want to compile against.

Since you keep saying Application the way you do... are you talking about on Macs? not using X11.app? thats not even controlled by Wine... you can set what X11 app is being used as your default for X11 requesting apps in the OS.

If your talking about something else, I just don't get it.

[Charles Davis]

On 3/11/10 7:44 AM, sonicfan1012 wrote:

I need to know how to edit wine so that it uses an application of another name rather than X11. The application of a different name is the same as X11, just a different name. But it's only the application. I have all the X11 files. I just need the name of the APPLICATION that it uses to not be X11 and to be another name.
Please don't think too hard about why I'm using an application with a different name that's the same as X11, you'll probly end up confusin urself just tell me how to change it so that wine will use an APPLICATION with a different name than X11.

That's right... You're the guy on a Mac who didn't like the fact that,
every time you ran Wine, X11 would start.

That's unavoidable right now. Wine NEEDS X11. Without X11, Wine won't
work. 'Nuff said.

However, I'm working on a solution to this. If this gets in, Wine on Mac
won't need X11 anymore. Stay tuned...

Seriously, though, if Wine needs X11, why are you so intent on replacing it?

[sonicfan1012]

On 3/11/10 7:44 AM, sonicfan1012 wrote:

I need to know how to edit wine so that it uses an application of another name rather than X11. The application of a different name is the same as X11, just a different name. But it's only the application. I have all the X11 files. I just need the name of the APPLICATION that it uses to not be X11 and to be another name.
Please don't think too hard about why I'm using an application with a different name that's the same as X11, you'll probly end up confusin urself just tell me how to change it so that wine will use an APPLICATION with a different name than X11.

That's right... You're the guy on a Mac who didn't like the fact that,
every time you ran Wine, X11 would start.

That's unavoidable right now. Wine NEEDS X11. Without X11, Wine won't
work. 'Nuff said.

However, I'm working on a solution to this. If this gets in, Wine on Mac
won't need X11 anymore. Stay tuned...

Seriously, though, if Wine needs X11, why are you so intent on replacing it?

uhh...i have a feeling you don't really understand my question, which makes sense. I'm still using X11. It's just a different name. The actual X11 application is blocked, but if I rename it to something different, it's unblocked. I just need to make wine use the X11 that I renamed instead of the X11 that is named X11. Otherwise, it doesn't work and it just says that X11 is blocked. But if I could make wine use the X11 that i renamed, then it would work. I just need to know how to do that.

For example, let's just say I copied my X11 and renamed it "WineX11". X11 doesn't work, but WineX11 does. But Wine always uses X11 instead. Despite the fact that I can open up WineX11, it doesn't matter, since wine is attempting to create an X server using the application X11. But if I can change it to use WineX11, then it would use that instead of X11. note that this name change is only for the APPLICATION X11, not like the X11 files in the library. It's just the APPLICATION. I'm pretty sure the other files are on my mac and don't need their names changed.

Oh and I should have mentioned this before, but I have a mac, with OSX 10.5 leopard

And again, I really don't know why this happens, it just does, lucky for me

[sonicfan1012]

Alrite, i'm sorry for double posting, but I just thought of an easy way to ask my question, and there's no edit button :\

Does anyone know if there is a file in wine that tells wine to look for X11.app, the application X11, and run it? There should be one, considering wine runs the application X11. My question is that I want to know where that file is and how to edit it so that it looks for an application with a different name. and remember that the application with a different name is just a copy of X11 under a different name, so wine should work just fine. I just really need to know where the file that searches for and runs X11.app is, and theoreticaly, wine would work.

[ryan woodsmall]

Alrite, i'm sorry for double posting, but I just thought of an easy way to ask my question, and there's no edit button :\

Does anyone know if there is a file in wine that tells wine to look for X11.app, the application X11, and run it? There should be one, considering wine runs the application X11. My question is that I want to know where that file is and how to edit it so that it looks for an application with a different name. and remember that the application with a different name is just a copy of X11 under a different name, so wine should work just fine. I just really need to know where the file that searches for and runs X11.app is, and theoreticaly, wine would work.

This has nothing to do with Wine. Your X11/Xquartz installation may be fouled up, or launchd/launchctl broken. There may be some answers on the Xquartz FAQ:

http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ

But your question would really be better answered on the Mac X11 users mailing list:

http://xquartz.macosforge.org/trac/wiki/MailingLists

[Charles Davis]

Oh I see. Sorry about that. You really should have done a better job of
explaining this in the first place.

OK, let me explain how this works to you. Wine doesn't really care what
your X server's file (or, in your case, bundle) on disk is called. When
it makes an X11 call, it expects an X server to be running. That's it.

If you do have an X server running, you can tell Wine to talk to it by
setting the DISPLAY environment variable to something appropriate.
Normally, that variable gets set for you. And that has to do with the
other situation...

...where there's NO X server running. On Mac OS, the reason X
automatically launches--or at least is supposed to automatically
launch--when Wine or anything tries to make an X11 call is that a
program called 'launchd' is waiting for someone to do this. 'launchd',
through a property list file (*.plist), knows the name of the X display,
so it exports it to the environment and waits for an X server call. When
it gets one, it launches X11 and forwards the call to it--after which
the X server functions like it does on Linux or any other system.

Therefore, if you want Wine to talk to your renamed X server, you need
to know the name of its display. Then you can set the DISPLAY
environment variable to that name so Wine can talk to the right X
server. It works the same way on Mac OS as it does on Linux, FreeBSD,
Solaris, etc.

HINT: If you start X11 from the command line, it will print the name of
the display to the console.

Chip

[sonicfan1012]

Oh I see. Sorry about that. You really should have done a better job of
explaining this in the first place.

OK, let me explain how this works to you. Wine doesn't really care what
your X server's file (or, in your case, bundle) on disk is called. When
it makes an X11 call, it expects an X server to be running. That's it.

If you do have an X server running, you can tell Wine to talk to it by
setting the DISPLAY environment variable to something appropriate.
Normally, that variable gets set for you. And that has to do with the
other situation...

...where there's NO X server running. On Mac OS, the reason X
automatically launches--or at least is supposed to automatically
launch--when Wine or anything tries to make an X11 call is that a
program called 'launchd' is waiting for someone to do this. 'launchd',
through a property list file (*.plist), knows the name of the X display,
so it exports it to the environment and waits for an X server call. When
it gets one, it launches X11 and forwards the call to it--after which
the X server functions like it does on Linux or any other system.

Therefore, if you want Wine to talk to your renamed X server, you need
to know the name of its display. Then you can set the DISPLAY
environment variable to that name so Wine can talk to the right X
server. It works the same way on Mac OS as it does on Linux, FreeBSD,
Solaris, etc.

HINT: If you start X11 from the command line, it will print the name of
the display to the console.

Chip

Wait wait WAIT SO...if I can get an X server to run (which I can, I just have to rename the X11 application and then X11 runs normally), then I can make wine "talk" with the X server that I just previously opened up??? And How do you set up the display environment variable appropriately to do this?

[sonicfan1012]

I'm sorry, I asked the wrong question. I meant to ask how to run X11 from the command line, since that shows the display name. I don't know how to do that though. And how exactly do i change the DISPLAY environment variable?

All this sounds very complex. Are you sure that there is no way to go into wine and change it so that it doesn't open the application X11 and instead opens another application that is the X11 application renamed? Oh and I don't think I'm actually renaming the x server; I'm just changing the application name X11 so that it becomes unblocked, and I want to change wine to use that renamed X11

however, I do appreciate your response, and if you really can't find a way to do the simpler way, then I'll just follow what you've been saying