[Image-SIG] Compiling PIL imaglibe 1.1.1 on Windows NT, using VC++ 6.0
Sat, 28 Oct 2000 15:39:07 -0500
Thanks for the (very prompt) help!
I stupidly didn't realise that "all C files" included files ABOVE the =
libImaging directory, and I also didn't search those files for the =
missing symbols! The failure of the types to work helped me to jump to =
the conclusion that the code had never been compiled on Windows. Sorry.
Anyways, after doing that, and messing with the search paths and library =
locations for a couple of iterations, it all compiled and linked.
----- Original Message -----=20
From: Fredrik Lundh <email@example.com>
Cc: Parzival Herzog <firstname.lastname@example.org>
Sent: Saturday, October 28, 2000 4:19
Subject: Re: [Image-SIG] Compiling PIL imaglibe 1.1.1 on Windows NT, =
using VC++ 6.0
> maybe you've misinterpreted the error message: these functions
> are defined in several places (stub versions in the core library, and
> Python-aware versions in the glue layer). for example:
> $ grep ImagingError_IOError *.c libImaging/*.c
> Building your own copy under Visual Studio should be =
> create a new project based on the sample extensions provided with
> Python (the target should be "_imaging.dll"), add all C files =
> "Except.c" and "coretest.c" to that project, check the contents of =
> "ImConfig.h" file (modify it if necessary), and build the DLL.
> in other words, remove Except.c, and everything should work.