Fullmoon build status

Questions, problems and discussion about compiling FreeOrion.

Moderator: Oberlus

Post Reply
Message
Author
cazfi
Space Floater
Posts: 42
Joined: Thu May 28, 2009 10:08 pm

Fullmoon build status

#1 Post by cazfi »

This thread is about how freeorion build with fullmoon ( http://www.cazfi.net/fullmoon/ ) works. For several years I have regularly spent some time to update everything to work again against freeorion development. My current system is Debian Wheezy x86_64-linux.

Current issues:

GiGi:
OIS vs ois header directory: viewtopic.php?f=24&t=6627 patch: http://svn.cazfi.net/fullmoon/trunk/exa ... iew=markup
Ambigious move_backward(): viewtopic.php?f=24&t=6581 patch: http://svn.cazfi.net/fullmoon/trunk/exa ... iew=markup
Building of test fail : viewtopic.php?f=24&t=6295 - patch: http://svn.cazfi.net/fullmoon/trunk/exa ... iew=markup

Now I face bunch of undefined boost symbols when linking against libGiGi.so. I do build boost myself (from HEAD of their version control) as part of freeorion build, so version is at least new enough :-) It might be too new, or simply broken, though.

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: Fullmoon build status

#2 Post by Geoff the Medio »

Try building against Boost 1.47. It's the last version I know works without problems on Windows, and some of the issues might be shared with other OSes on newer versions of Boost.

cazfi
Space Floater
Posts: 42
Joined: Thu May 28, 2009 10:08 pm

Re: Fullmoon build status

#3 Post by cazfi »

cazfi wrote:Now I face bunch of undefined boost symbols when linking against libGiGi.so. I do build boost myself (from HEAD of their version control) as part of freeorion build, so version is at least new enough :-) It might be too new, or simply broken, though.
This problem was indeed outside freeorion/GG. I were not linking against correct boost libraries, but it found system boost after all, and even worse; I were linking against libraries incompatible with headers (that were correctly) used.

For others to avoid same mistake:
I had

Code: Select all

cmake -DCMAKE_INSTALL_PATH=<PATH TO MY BOOST/include> -DCMAKE_LIBRARY_PATH=<PATH TO MY BOOST/lib>
This found headers correctly, but system libraries were still prefered over my own ones.
I now use

Code: Select all

cmake -DBOOST_ROOT=<PATH TO MY BOOST> -DBoost_NO_SYSTEM_PATHS=true
GG now compiled, I'm off to compile FreeOrion itself.

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: Fullmoon build status

#4 Post by Geoff the Medio »

I don't know what Fullmoon is, but if your experiences are at all relevant for general Linux or Ubuntu builds, it'd be nice if you could update the wiki Linux compile page as well.

Post Reply