As I do not know whether this mail reached the original poster - I could not find the listserver in the TO address -
I allow to send it forward to the list.
Here also an explanation of how to generate and check preprocessor output, from the MSDN Library
(under C/C++ Preprocessor Reference, The Preprocessor)
Microsoft Specific
You can obtain a listing of your source code after preprocessing by using the /E or /EP compiler option. Both options invoke the preprocessor and output the resulting text to the standard output device, which, in most cases, is the console. The difference between the two options is that /E includes #line directives and /EP strips these directives out.
END Microsoft Specific
This is good practise to see how the preprocessor modifies the sourcecode, and usually helps to track down
such problems.
Peter
-----Original Message-----
From: Patricia J. Hawkins [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 27, 2002 3:57 PM
To: Frey, Peter
Subject: Re: swig help with wtsapi32
>>>>> "PF" == Peter Frey <[EMAIL PROTECTED]> writes:
PF> Hi Mark,
PF> I have no experience with SWIG but we used Boost.Python to wrap a C++
PF> framework.
PF> And I know C++.
PF> The error looks like it is a problem of your project configuration, i.e.
PF> somebody is defining the symbols before WtsApi32.h is processed by the C/C++
PF> preprocessor. Or the header file is included twice.
Yes, I'd try running it through just the preprocessor, using current
flags, and see that doesn't make all clear.
--
Patricia J. Hawkins
Hawkins Internet Applications, LLC
