Hi,
On Thu, Jan 22, 2009 at 1:01 AM, Gerrit Voss <[email protected]>wrote:
>
> You have to be a little bit careful, some cmake settings are only made
> once in the very beginning, so if you just keep updating from the svn
> without redoing cmake from scratch (e.g. at least delete the cache) you
> will not pick up all the changes. This is mainly due to the fact that
> you can only set the compiler once in the beginning. Thereafter cmake
> does not allow you to modify you compiler choice any more, hence we also
> run our compiler setup once in the very beginning. IIRC this came
> quite straight out of the cmake FAQ. Last variable values from the cache
> win over variables from the CMake files, unless you force the issue, but
> than the user can't change anything any more as the force option will
> always win.
>
> And the crt handling definitely changed during the last few commits in
> order to support building all variants from Visual Studio without the
> need to rerun cmake. So if you haven't, can you delete your cache and
> see if cmake picks up all the changes so you can build without modifying
> the compiler setting.
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.
BTW, the compilation is working now even with fcd2code enabled, thanks!
Best regards,
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
