Home Original page

Problem building Win32 extensions

Mark Hammond MarkH at ActiveState.com
Tue Oct 17 23:10:10 EDT 2000 
Yes - it sounds like the exact same problem.

You will probably find you "python.swg" is causing the 'extern "C"'
around the Python.h #include.  Simply remove this - python.h
internally does this where necessary...

The python.swg under my CVS tree is correct - make sure SWIG are using
the .i files in the SWIG CVS dir.

Mark.

--
markh at activestate.com - but if you think I speak for them, you dont
know Dick!

"Charles Medcoff" <cmedcoff at sprynet.com> wrote in message
news:8sivth$tij$1 at slb0.atl.mindspring.net...
> This sound like a problem similar to what I went through a couple of
> versions ago.  (I confess that I haven't built from the the source
> latetly.).
>
> Try modifying the python.swg file in the PyWin32 directory and make
sure
> that the include for python.h is in the right place.
>
> The problem I had is that the contents of the python.swg file was
placed in
> SWIG generated source files.  This always created the compiler
errors that
> you describe.
>
> Have a look at the win32 mailing list archives for a long thread
between I
> and other on this problem.
>
>
More information about the Python-list mailing list