ggazzo / opennero

Automatically exported from code.google.com/p/opennero
Other
0 stars 0 forks source link

scripting/exports.cpp is large and difficult to compile. #126

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
To Reproduce
1. Get SVN version as described on the wiki.
2. Run cmake and make in a build directory

The compile process was complete to 95% when exports.cpp began to compile. 
Several hours later it was not compiled and my system was horribly unresponsive.

Using SVN trunk version of OpenNERO on Ubuntu 11.10

My computer is severely under powered (256k of RAM) and I am not sure if 
OpenNERO will even run under it, but as far as my knowledge of C++ goes, that 
should not affect compiling, especially compiling of a file in the "scripting" 
directory.

Original issue reported on code.google.com by jaccar...@gmail.com on 5 Dec 2011 at 5:48

GoogleCodeExporter commented 9 years ago
That file is unfortunately very large and memory-intensive to compile because 
of the Boost.Python templates. We should break it up into several more 
manageable chunks. As is, we have to use /bigobj on Windows - I wonder if there 
is a similar option for gcc.

Original comment by ikarpov on 6 Dec 2011 at 2:12

GoogleCodeExporter commented 9 years ago
I can now confirm that my computer was too old. On a MacBook Air running 
Ubuntu, it's compiling just fine!

Original comment by jaccar...@gmail.com on 3 Feb 2012 at 6:46

GoogleCodeExporter commented 9 years ago

Original comment by ikarpov on 1 Sep 2013 at 7:10