Re: Gimp 1.3 compile and link dependencies

2001-02-05 Thread Hans Breuer
At 04:13 05.02.01 +, Nick Lamb wrote: On Mon, Feb 05, 2001 at 02:26:23AM +0100, Hans Breuer wrote: The windoze version of gimpwidgefts can't include two symbols for different implementation of the same function. There is only one version of the dll in memory, even if loaded by another

Re: Gimp 1.3 compile and link dependencies

2001-02-05 Thread Hans Breuer
At 16:02 05.02.01 +0100, Michael Natterer wrote: Hans Breuer [EMAIL PROTECTED] writes: On Mon, Feb 05, 2001 at 02:26:23AM +0100, Hans Breuer wrote: The windoze version of gimpwidgefts can't include two symbols for different implementation of the same function. There is only one version of

Gimp 1.3 compile and link dependencies

2001-02-04 Thread Hans Breuer
while adapting make and export definition files for the win32 build of Gimp 1.3, there where some questions ariseing : - what are the supposed dependency between all the libgimp* libraries ? what I have at the moment is (gimp.exe works, but most plug-ins do not yet) : gimp.exe

Re: Gimp 1.3 compile and link dependencies

2001-02-04 Thread Sven Neumann
Hi, Hans Breuer [EMAIL PROTECTED] writes: while adapting make and export definition files for the win32 build of Gimp 1.3, there where some questions ariseing : - what are the supposed dependency between all the libgimp* libraries ? you got it right in your graphics below. what I

Re: Gimp 1.3 compile and link dependencies

2001-02-04 Thread Hans Breuer
At 01:31 05.02.01 +0100, Sven Neumann wrote: Hans Breuer [EMAIL PROTECTED] writes: ... all the above resolves fine except libgimwidgets dependcies, because there are the functions listed below, which need (and have) different implementations in Gimps and Plug-Ins context. Currently I'm

Re: Gimp 1.3 compile and link dependencies

2001-02-04 Thread Nick Lamb
On Mon, Feb 05, 2001 at 02:26:23AM +0100, Hans Breuer wrote: The windoze version of gimpwidgefts can't include two symbols for different implementation of the same function. There is only one version of the dll in memory, even if loaded by another process. The code is shared across process