[Bf-committers] solving the issues of switching to python 2.4on Os X for next release

[Joseph Gilbert]

Hmm. kk well im not exactly sure but it seems to me that your having a 
problem with the c/c++ headers. I found someone witha similar problem:
http://gcc.gnu.org/ml/libstdc++/2003-01/msg00210.html
It's hard to say where this is coming from, maybe the standard library 
headers being pulled in by Python.h. Im sure there is a solution out 
there :) As stivs pointed out though it's an issue that the gameengine 
developers will need to hammer out.

Hans Lambermont wrote:

>Gilbert, Joseph wrote:
>
>  
>
>>Python.h should always be declared before anything else because it sucks
>>in a bunch of standard library headers. I don't know if this is your
>>problem or not.  Also I remember that <iostream.h> is not kosher for
>>c++. Prob should change this to <iostream>.
>>
>>#include "Python.h"
>>#include <vector>
>>#include <iostream>
>>
>>might be better.
>>    
>>
>
>Changing iostream.h to iostream does not help :
>
>g++ -I /usr/local/include/python2.4 a.c
>In file included from /usr/include/c++/3.4/ios:48,
>                 from /usr/include/c++/3.4/ostream:45,
>                 from /usr/include/c++/3.4/iostream:45,
>                 from a.c:3:
>/usr/include/c++/3.4/bits/localefwd.h:58:34: macro "isspace" passed 2 arguments, but takes just 1
>In file included from /usr/include/c++/3.4/ios:48,
>                 from /usr/include/c++/3.4/ostream:45,
>                 from /usr/include/c++/3.4/iostream:45,
>                 from a.c:3:
>/usr/include/c++/3.4/bits/localefwd.h:58: error: `std::isspace' declared as an `inline' variable
>...
>
>And changing the include *order* is not easy, these 3 include files are the
>result of several other includes. See my earlier posts.
>
>-- Hans
>_______________________________________________
>Bf-committers mailing list
>Bf-committers at projects.blender.org
>http://projects.blender.org/mailman/listinfo/bf-committers
>  
>