From: valtul@demos.su (Valery Tulnikov) Subject: RE: GIMP anyone? 30 Jun 1998 04:50:16 -0700 Message-ID: <000301bda3b1$e4607ef0$991157c2.cygnus.gnu-win32@dialup.ru> References: <199806291842.LAA28603@mailwall.nwest.mccaw.com> Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit To: Cc: "Cygwin List" Two remarks: Firstly, there is a function in Gimp --no-shm that you could use when starting a program - it's work for me on FreeBSD (everyone could see that the Gimp's loading is significantly slow down), but it's no work on Cygwin with or without IPC package - it's hanging up in script-fu module. Did you try to comment all shm things out? It'll be the greate contribution to Cygwin ported application list. The second: it could be more efficient to produce a shared dll for GTK and Gimp - it takes over 50 mb on my hard drive - too much for buggy port! With best regards, Valery Tulnikov, valtul@demos.su http://www.dol.ru/users/valtul -----Original Message----- From: Alexander Stockdale [mailto:astockdale@computer.org] Sent: 29 ???? 1998 ?. 22:39 To: valtul@demos.su Subject: RE: GIMP anyone? > It's compiled out of box. But GIMP use shared memory calls - there no > support in Cygwin for shared memory. Someone develops external package for > that (see http://www.multione.capgemini.fr/tools/pack_ipc/) but it's not > functioned very well and need additional developer efforts to work properly. > Anyway, if you need that buggy version of GIMP let me know. > The GIMP code is written in such a way that you can pretty much comment out any calls to shm functions (requires a little intelligence, but not a lot). The GIMP will just assume that shm is not working on your machine, and work around the lack of shared memory. Alexander Stockdale - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".