Thorsten Froehlich wrote:
> 
> > Interesting idea but sadly the povray source files are inconsistent about
> > order of the #include's for project specific and general files - placing
> > this in frame.h would not work.
> 
> Yes, it would.  frame.h will always be the first POV-Ray include file
> included.

frame.h is the first of the POV-Ray include files but the standard include
files are sometimes before, sometimes after them.

> Anyway, maybe instead of chaging POV-Ray, how about simply not including the
> Windows header files?  At least the one that is causing the problems.  After
> all, they are obviously not needed to compile the Unix version....
> 

In file included from /usr/include/w32api/windows.h:97,
                 from
/usr/include/c++/3.2/i686-pc-mingw32/bits/gthr-default.h:462,
                 from /usr/include/c++/3.2/i686-pc-mingw32/bits/gthr.h:98,
                 from
/usr/include/c++/3.2/i686-pc-mingw32/bits/c++io.h:37,
                 from /usr/include/c++/3.2/bits/fpos.h:44,
                 from /usr/include/c++/3.2/iosfwd:46,
                 from /usr/include/c++/3.2/bits/stl_algobase.h:70,
                 from /usr/include/c++/3.2/algorithm:66,
                 from config.h:64,
                 from frame.h:58,
                 from blob.cpp:94:
/usr/include/w32api/winsock2.h:27: ...

So unless i want to modify the standard header files...

In this case Warp's suggestion would help but some files (like
'fnpovfpu.cpp') have '#include <algorithm>' before '#include "frame.h"'

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 02 Nov. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message