Re: [Gimp-developer] GIMP on Mac OS X
On Fri, Dec 26, 2003 at 06:59:57PM +0100, Sven Neumann wrote: Porting GTK2 to Quartz could bring some improvements but it isn't a prerequisite for a good user experience of The GIMP on Mac OS X. The one thing that is a lot more important at the moment is to fix bug #102058: http://bugzilla.gnome.org/show_bug.cgi?id=102058 The fact that our shared memory implementation doesn't work on Mac OS X makes our plug-ins run unreasonably slow. This will hurt the user experience a lot more than widgets being drawn by an X11 server which is available, working, supported and fast. So if you think about helping to push GIMP-1.3/2.0 on Mac OS X, you should consider to help us to implement shared memory using mmap or using POSIX shm. I just checked in an POSIX shm tile transport implementation. I'd like someone on OS X to test it, since I'm not 100% sure how POSIX compliant OS X is, but I'm reasonably sure it works. It was rather trivial to do, I'm surprised no OS X user took the initiative to fix this long ago. -Yosh ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] OS X build from CVS: Illegal reference
Hi, Terje Tjervaag [EMAIL PROTECTED] writes: I was wondering if anyone had seen this before: I haven't but my guess is that it's a problem with your version of libtool. When you build from a tarball, you are using the included version of libtool which has been 1.5 in the recent tarballs. When you build from CVS, the system-wide libtool is used to libtoolize the source tree. I heard that setting LIBTOOL=glibtool (or similar) helps on OS X. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: GIMP Aqua GTK+OSX
On Thu, Dec 25, 2003 at 02:12:22PM -0800, Robin Rowe [EMAIL PROTECTED] wrote: As documented in our HOWTO, GIMP code is using quote marks instead of angle brackets when including some GTK library header files. That should not work. If that is true, the gimp developers would be rather happy for reports or patches about that, I am sure. Especially as writing a HOWTO entry is probably _more_ work than just going in and fixing the relevant parts. As I'm the official project leader for GTK+OSX and posted here representing Woaw, impressive! surprise us just once by reacting positively when somebody from our team does something that benefits your project? Frankly, writing howto entries on how broken the gimp codebase is is not benefitting gimp very much. Or did I miss something very obvious? Apologies if that is the case. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
