Re: MacPorts vs xquartz? (was Re: openmotif in macports dependencies and xquartz?)
Re: MacPorts vs xquartz? (was Re: openmotif in macports dependencies and xquartz?)
- Subject: Re: MacPorts vs xquartz? (was Re: openmotif in macports dependencies and xquartz?)
- From: Tommy Bollman <email@hidden>
- Date: Sun, 03 Apr 2011 02:44:53 +0200
Hello.
Oops I forgot to include the contents of org.x.privileged_startx.plist file for the sake of completedness.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
<plist version="1.0">
<dict>
<key>EnableTransactions</key>
<true/>
<key>Label</key>
<string>org.x.privileged_startx</string>
<key>MachServices</key>
<dict>
<key>org.x.privileged_startx</key>
<true/>
</dict>
<key>ProgramArguments</key>
<array>
<string>/usr/X11/lib/X11/xinit/privileged_startx</string>
<string>-d</string>
<string>/usr/X11/lib/X11/xinit/privileged_startx.d</string>
</array>
<key>TimeOut</key>
<integer>120</integer>
</dict>
</plist>
Have a nice evening.
Den 2. apr. 2011 kl. 20.48 skrev Jeremy Huddleston:
> Yeah, you're definitely setting DISPLAY somewhere in your environment.
>
> Check out the DISPLAY debugging info on the XQuartz FAQ:
>
> http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ#sshXforwardingdebugging
>
>
>
> On Apr 2, 2011, at 11:39, Tommy Bollman wrote:
>
>> Hello Bayard.
>>
>> I installed a "bare" vim, -at least one without x-support, and I can't reproduce the problem right now.
>>
>> I did tried the command with xterm through XQuartz and I got :0 as the result when I did the ps command on xterm.
>>
>> I have some discrpancies regarding the $DISPLAY :
>>
>> Its from my log. Localhost [0x0-0x11d11d].org.macosforge.xquartz.X11[0]: xauth: (argv):1: bad display name "Localhost.local:0" in "remove" command
>>
>> I did a full trace on startx and initx once, and then there popped up display names of (i believe)
>> Localhost.local/unix:0.
>> I just hadn't the time to deal with it then. I don't have that time now neither, because I can't remember where I put that echo statement do reveal the display parameter.
>>
>> This may have nothing to do with those problems I addressed in this thread, but as soon as I get around to it, i'll file a ticket or something, in ordre to understand what is happening here.
>>
>> I am rather new to this, and I thought that XQuartz is to replace X11 as an X-server am I right?
>>
>> Thanks anyway, I'll comeback to this when I have the time.
>>
>> Den 2. apr. 2011 kl. 19.02 skrev Bayard Bell:
>>
>>> Are you able to check your DISPLAY environment variable for each application by comparing the output of ps -Exww -p <pid> for each process? I believe the normal way that Apple defines their X listeners is as LaunchAgents with SecureSocketWithKey, which creates a domain socket in a randomly named directory created by launchd for each session, whose name is inherited by those jobs but not the user.
>>>
>>> As well as the DISPLAY variable, you can use the open command to specify which Xserver you want to use (e.g. open -a XQuartz.app /opt/local/bin/xemacs). My understanding is that you have to create new app and/or bundle names for this to spawn additional Xserver instances, otherwise you'll use what's already there if it's running or launch it if it's not.
>>>
>>> On 2 Apr 2011, at 17:18, Tommy Bollman wrote:
>>>
>>>> Hello Jeremy.
>>>>
>>>> The problem I had was that I installed the +huge port of vim.
>>>>
>>>> I have a good setup of xterm from within xterm. ( I start XQuartz from spotlight).
>>>>
>>>> When I then started up vim from withing the xterm, giving the command "gu", then X11.app
>>>> would start and do the window handling for vim I believe.
>>>>
>>>> The result was that I ended up having both X11.app and XQuartz.app visible in the command bar. (The one I get when I press cmd-Tab ).
>>>>
>>>> I think the problems goes for other apps as well.
>>>>
>>>> Since then I have installed a port which doesn't use X11, and MacVim, but I really would like
>>>> to have the menus and such from within XQuartz.
>>>>
>>>> I wonder how I fix this, so that vim/xim only uses XQuartz as the window server.
>>>> -If the problems would go away if I recompile, using the libraries found in the /opt tree?
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Den 1. apr. 2011 kl. 03.30 skrev Jeremy Huddleston:
>>>>
>>>>>
>>>>> On Mar 31, 2011, at 4:52 PM, Tommy Bollman wrote:
>>>>>
>>>>>> Hello.
>>>>>> Can I read this as I might manage to get vim/xim building with only macports libraries and not the ones shipped with Apple
>>>>>
>>>>> Yes. That is the policy in MacPorts (to prefer in-tree dependencies rather than system-provided ones).
>>>>>
>>>>>> -And make it work without firing up X11.app ?
>>>>>
>>>>> I'm not sure what you're asking... You could use any X server you want...
>>>>>
>>>>>>
>>>>>>
>>>>>> Den 31. mars 2011 kl. 23.25 skrev Jeremy Huddleston:
>>>>>>
>>>>>>>
>>>>>>> On Mar 31, 2011, at 11:01 AM, Philip J. Schneider wrote:
>>>>>>>
>>>>>>>> Kinda highjacking my own thread here... :-)
>>>>>>>>
>>>>>>>> Considering Jeremy's feedback, I downloaded openmotif and all its dependencies, and so I can now build/run an X11 app using MacPorts-provided headers and libs. (That is, with only /opt/local-based paths specified in XCode.)
>>>>>>>>
>>>>>>>> A few questions:
>>>>>>>>
>>>>>>>> 1. In very general terms, how do the xquartz-provided X includes and libs differ from those provided by MacPorts? Pro/con on using one vs the other?
>>>>>>>
>>>>>>> The ones in MacPorts are generally the latest versions.
>>>>>>> The ones from XQuartz are also generally the latest version as of the release date.
>>>>>>> The ones from Apple are a bit more dated / stable for consistency across major releases of the OS.
>>>>>>>
>>>>>>>> 2. If one did want to distribute an X11 application that needed one or more X-related libraries not provided by the default system (e.g. openmotif), what would be the recommended approach? I might wish to assume that the users would not want to build up their own fink or MacPorts installation... :-)
>>>>>>>
>>>>>>> I'd recommend using the host X11 libraries. Link your application (including extra libraries) against those, and ship everything not part of the system. You could use something like /opt/myapp as the prefix for building all your bits and just ship /opt/myapp (and probably place /opt/myapp/bin into $PATH via /etc/paths.h/myapp
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>> X11-users mailing list (email@hidden)
>>>>>>>
>>>>>>> This email sent to email@hidden
>>>>>>>
>>>>>>
>>>>>> Best regards
>>>>>>
>>>>>>
>>>>>>
>>>>>> Tommy Bollman
>>>>>> --------------------------------------------------------------------------------------------------
>>>>>> Mollison's Bureaucracy Hypothesis:
>>>>>> If an idea can survive a bureaucratic review
>>>>>> and be implemented it wasn't worth doing.
>>>>>>
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> X11-users mailing list (email@hidden)
>>>>>>
>>>>>> This email sent to email@hidden
>>>>>>
>>>>>
>>>>>
>>>>
>>>> Best regards
>>>>
>>>>
>>>>
>>>> Tommy Bollman
>>>> --------------------------------------------------------------------------------------------------
>>>> Mollison's Bureaucracy Hypothesis:
>>>> If an idea can survive a bureaucratic review
>>>> and be implemented it wasn't worth doing.
>>>>
>>>> _______________________________________________
>>>> macports-users mailing list
>>>> email@hidden
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>>
>>
>> Best regards
>>
>>
>>
>> Tommy Bollman
>> --------------------------------------------------------------------------------------------------
>> Mollison's Bureaucracy Hypothesis:
>> If an idea can survive a bureaucratic review
>> and be implemented it wasn't worth doing.
>>
>> _______________________________________________
>> macports-users mailing list
>> email@hidden
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>
> _______________________________________________
> macports-users mailing list
> email@hidden
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
Best regards
Tommy Bollman
--------------------------------------------------------------------------------------------------
Mollison's Bureaucracy Hypothesis:
If an idea can survive a bureaucratic review
and be implemented it wasn't worth doing.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden