Hi,

Thiago Bastos wrote:
> Hi,
> 
> On Thu, Jan 22, 2009 at 10:01 PM, Gerrit Voss <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>     Are the support libs build with the correct runtime
>     settings (/MD /MDd) ?
> 
> 
> Yes, this was the first thing I checked.

ok


>     I'm not sure if I ever tried static libs, but IIRC whatever
>     support lib I build for Windows I made sure it had the correct runtime
>     setting. Otherwise function names change and I don't want to mix static
>     and dynamic runtime libs.
> 
> 
> Indeed. What's even stranger is that it found 95% of the functions from 
> the CRT (malloc, memcpy, etc.).
> It only complains about a small subset of the functions, mostly 
> non-ansi, posix functions. But that AFAIK are part of the CRT all the same.

the only other idea I have left is that the windows version defines
don't add up.

>     Hmm, #1 for OpenSG libs is strange, which OpenSG library/code has a
>     problem ? Could you post (send me) the unresolved symbol messages from
>     the compiler.
> 
> 
> I'm sorry, I was wrong. I reviewed everything and all messages are 
> caused by support libs.
> Those that I thought were caused by OpenSG were actually caused by VTK...

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.

> 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.

kind regards,
   gerrit





------------------------------------------------------------------------------
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

Reply via email to