Hi,
On Fri, Jan 23, 2009 at 12:10 AM, Gerrit Voss <[email protected]>wrote:
>
> ok, that one I too only tried on Linux ;-(. I'll see if I find some
> time to try Windows. Short question are you using dynamic or static vtk
> libs.
Static. All libs are static except for glut and libtiff (GLUT was
precompiled, and I didn't mind hacking the makefile for libtiff).
> At least now we know of the potential problems of combining
> > statically-linked support libs with the standard CMake linker flags :-)
> > No idea if this is something easy to improve on your side...
>
> the only 'real' solution I see is to go the VTK way and provide the
> support libs in a way that you can build them together with OpenSG using
> the same settings. Windows seems to fragile to test for all possible
> combinations ;-(. So at least providing on option where we can have
> reasonable good control over the environment is the best solution I
> can see right now.
It'd be nice if the support libs were distributed and integrated into the
build on Windows (but stick to system libs on Linux). It was quite painful
to gather and manually compile all dependencies on Windows, as nobody seems
to provide good precompiled binaries.
But then, I believe a preliminary simple solution would be to remove
"/nodefaultlib" and add "advapi32.lib" to the list of libs in
SetupCompiler.cmake. This would make the build work correctly with both
static and dynamic libs. Do you think "/nodefaultlib" is really required?
Thanks,
Thiago
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
