Hi Mark, I don't have any Mingw experience, but generally the wrappers do consume alot of memory, this is a consequence of all every method having a mini class constructed for it, and templates being used to do this. Under linux all the wrappers compiled takes up 120Mb on my machine, the largest single wrapper being osgwrapper_osg.so at 60Mb. Ouch, this is over 20 times bigger than libosg.so. To C++'s lack of inbuilt introspection we can lay the blame for this...
What to do about in under Mingw... you could try compiling with the min size build option - see CMAKE_BUILD_TYPE when you run ccmake ., or CMakeSetup.exe. Or perhaps a later gcc compiler would fix it. Robert. On 5/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi, I am trying to build 1.9.4 with MinGW. However when it gets to creating the wrapper DLLs, the linker, ld, takes a very large amount of memory (>200MB) and after about an hour it aborts with a memory allocation failure. Everything else seems to compile and work correctly and I certainly have enough memory. Even trying to link with just Geometry wrapper obj into my application, it doesn't get past the linking phase. I can create a DLL from a very small subset of the osg wrapper objects (excluding Geometry). Has anyone encountered this before? What is special about the wrappers that leads to this problem (I am no C/C++/MinGW/DLL expert). Would a particular ld flag get around the problem? Yes, I am 90% certain I have to use MinGW. I am integrating with Haskell which uses MinGW as part of its backend. Cheers Mark _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
