From: nordwick AT scam DOT XCF DOT Berkeley DOT EDU ("Jay Nordwick")
Subject: Re: Gimp on gnuwin32
21 May 1997 22:37:31 -0700
Sender: mail AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199705211717.KAA19153.cygnus.gnu-win32@cygnus.com>
Original-To: banders AT switch DOT rockwell DOT com
Original-cc: gnu-win32 AT cygnus DOT com, nordwick AT scam DOT XCF DOT Berkeley DOT EDU
In-reply-to: Your message of "Tue, 20 May 1997 09:23:36 CDT."
             <3381B3E8 DOT 5B5B AT switch DOT rockwell DOT com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7702 DOT 864233719 DOT 1 AT scam DOT XCF DOT Berkeley DOT EDU>
Original-Sender: owner-gnu-win32 AT cygnus DOT com

"Has anyone gotten Gimp (Linux image processing) to work with gnuwin32?

First, it is not Linux image processing, it is general unix based.
In the lab we have it running on FreeBSD, Solaris, HP-sUX, Digital
Linux, etc....

Pete and Spencer (the main GIMP programmers) were thinking of doing
a native win32 version (actually, having someone else do it).  The
thought is that a porting library will be too slow, since there
are quite a few fork/vfork calls (at least one for each plugin opperation)
and alot of the X/shm is very platform specific.

"If so were there any tricks/patches required? Any advice?
"I'm pretty early into trying to get it to work, but it takes a day for
"my email to be posted, so I play the field.

Yeah, my advice: wait for the 1.0 release that should be less than three
months away.  There is no need porting it until then.  Also a native port
is almost a necessity, since the gimp is very performace based: it is,
after all, a photoshop emulator (read: wanna-be) and you wouldn't want
photoshop to be built using a porting library would you ?  That would be
too painfully slow.

jay
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".