OK - this sounds very good.
If you can think of any more or more specifics just let me know.
On May 4, 2011, at 3:41 AM, Christophe Fergeau wrote:
On Tue, May 03, 2011 at 05:32:12PM -0500, Cliff Sharp wrote:
So, now I use the X11 environment that comes with osx when I actually run
spiced
On Wed, May 04, 2011 at 09:17:37AM -0500, Cliff Sharp wrote:
OK - this sounds very good.
If you can think of any more or more specifics just let me know.
To make things clear, these are things that I'd love to have in spice-gtk
(I assume spice-gtk maintainers agree with this, but maybe they
I have not resolved these issues from below with MacPorts x11 or Xquartz. I am
still getting these errors in the /var/log/system.log file when trying to run
any x application.
But, I was able to work around these problems.
I used launchctl -w to disable macports x11 and xquartz entries. This
On Tue, May 03, 2011 at 03:34:07PM -0500, Cliff Sharp wrote:
I have not resolved these issues from below with MacPorts x11 or Xquartz.
I am still getting these errors in the /var/log/system.log file when
trying to run any x application.
But, I was able to work around these problems. I used
I agree totally.
What I am doing is using MacPorts to download all the software ports, that are
available for osx, to use to build spicec and spice-gtk successfully -
including xorg. BTW - there is only one package that is not in MacPorts in
order to build spice-gtk and that is celt051.
I
