o.k. this is SWIG specific now
if it contains an own preprocessor you have to check what it does with the header files
the documentation given is only if you are using Visual C++ (what is the case with the Boost.Python approach)
I don't know what preprocessor SWIG is using (probably its own one)
so sorry my reply was no help
> -----Original Message-----
> From: Roach, Mark R. [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 27, 2002 4:30 PM
> To: Frey, Peter
> Cc: [EMAIL PROTECTED]
> Subject: Re: FW: swig help with wtsapi32
>
>
... <cut/>
>
> I don't think I understand. I don't have any project files, all I have
> is a header file for the microsoft terminal services api (wtsapi32)
> which I want to wrap in python, similar to the other win32 extensions:
> win32api etc. Am I missing a big step? Do I need MSVC? I was
> planning on
> just using my current mingw setup.
>
> I thought that it goes something like this:
>
> wtsapi32.h + swig -> wtsapi32.py wtsapi32module.c
>
> which I then compile against the python headers to generate a
> module. Is
> there more to it than this?
>
> Thanks,
>
> Mark
>
