On Fri, May 2, 2008 at 8:18 PM, Christopher Barker
<
Chris.Barker@...> wrote:
> Mathieu Malaterre wrote:
>
> > I am getting this annoying error message when compiling a swig-python
> module:
> >
>
> How are you compiling the module? distutils shouldn't give you this sort of
> error.
I am using cmake + VS Studio Expres. So _DEBUG is being defined, and I
actually would need this to work around some crazy vs9 checking:
# ifdef _DEBUG
# undef _DEBUG
# if defined(_MSC_VER) && _MSC_VER >= 1400
# define _CRT_NOFORCE_MANIFEST 1
# endif
# include <Python.h>
# define _DEBUG
# else
# include <Python.h>
# endif
#
The only solution I can think of, is have a fake Python.h that is
found first in the search path...but I am pretty sure people have seen
this before, and there must be another work around.
Thanks,
--
Mathieu
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
Swig-user mailing list
Swig-user@...
https://lists.sourceforge.net/lists/listinfo/swig-user
