Hi,

Thiago Bastos wrote:
> Hi,
> 
> On Thu, Jan 22, 2009 at 1:01 AM, Gerrit Voss <[email protected] 
> <mailto:[email protected]>> wrote:
> 
> 
> 
> Well, I usually (if not always) clear the cache file.
> Just to be sure I re-did the whole compilation process here, starting 
> from a clean cache, and got the compiler errors I previously stated 
> (unresolved external symbols: strdup, lfind, read, write, lseek, close, 
> RegCloseKey, etc.).
> 
> To solve problems I had to:
> 1) Remove "/nodefaultlib" from the CMAKE_*_LINKER_FLAGS, as previously 
> mentioned.
> 2) Add advapi32.lib to CMAKE_[C/CXX]_STANDARD_LIBRARIES (forgot to 
> mention this the last time)
> 
> I believe step #2 is only necessary because I'm using statically-linked 
> versions of zlib/tiff/png/jpeg (and some of them call functions from 
> advapi32.lib to manipule the windows registry). 
 >
> But step #1 is required even by some of the OSG libraries.

Are the support libs build with the correct runtime
settings (/MD /MDd) ?

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.

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.

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