Sigh. But this is not yet a working fix--we don't know how to get
code compiled with VS 2005 to work with Python 2.5. I wonder if
Python 2.6 would solve the problem.
Randolph
On Nov 26, 2008, at 1:42 AM, Hartmut Seichter wrote:
I have a student working on this problem - to add the flag is good
and fixes the problem temporarily but in general osgSWIG needs a
more scalable approach.
H
Randolph Fritz wrote:
I'm writing this up so that people who aren't cmake experts have a
note about this workaround.
For my next trick, I tried building this on Windows using Visual C+
+. After some blundering around, I found that adding /bigobj flag
to CMAKE_CXX_FLAGS (edit the field in the cmake GUI--it is one of
the "advanced" options) makes the build go, but only on Visual
Studio 2005 and later.
MS acknowledges the problem and recognizes that machine-generated
code may trigger it in the page at <http://msdn.microsoft.com/en-us/library/ms173499(VS.80).aspx
>.
Reported at <http://code.google.com/p/osgswig/issues/detail?id=13>.
Randolph Fritz
design machine group
architecture department
university of washington
[EMAIL PROTECTED]
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
--
Hartmut Seichter, PhD (HKU), Dipl-Ing.(BUW), Postdoctoral Fellow,
HITLabNZ
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
