If you search our forums (upper right of page) for FreeOrionVersionString, you'll find a thread with a couple potential fixes (the simplest has to do with changing the build location).
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
ok well can you tell us what potential fixes you tried from that other thread, and how your situation matches or not? What cmake version and boost versions are you using? Did you try an out-of-source build?
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
Dilvish wrote:ok well can you tell us what potential fixes you tried from that other thread, and how your situation matches or not? What cmake version and boost versions are you using? Did you try an out-of-source build?
Ah, yeah, I think I see the issue, your build directory is all the way out of your local git repo. When we had been using the phrase "out-of-source" build, it really meant something more like "compartmentalized from the source files" not "totally out of the source tree". Try
Dilvish wrote:Ah, yeah, I think I see the issue, your build directory is all the way out of your local git repo. When we had been using the phrase "out-of-source" build, it really meant something more like "compartmentalized from the source files" not "totally out of the source tree". Try
pheldens wrote:Don't put the build dir inside the git source tree! Put it outside at the same level as the source tree, to prevent a build bug.
The location I suggested is the default for KDevelop, and has never caused me any trouble (though it is best to then add that add it to .gitignore). The location you suggest appears to me to be the exact one that had been causing AndrewW trouble.
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
OK, the Compile in Linux wiki page still contains references to Bullet and Ogre3d that need removing. It needs adding that you need SDL2 and not 1.2 (which comes with Kubuntu), so
Now I can't get it to install because it wants me to have Glew. I've downloaded Glew, but can't figure out how to get it into the right place, so I'm taking a break, if anyone knows, brilliant, I'll get on with it when I've watered the garden
Mat Bowles
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
MatGB wrote:OK, the Compile in Linux wiki page still contains references to Bullet and Ogre3d that need removing. It needs adding that you need SDL2 and not 1.2 (which comes with Kubuntu), so
will grab that.
Now I can't get it to install because it wants me to have Glew. I've downloaded Glew, but can't figure out how to get it into the right place, so I'm taking a break, if anyone knows, brilliant, I'll get on with it when I've watered the garden
right, there have been a lot of people running into that; it's why I just added to the compile instructions a recommendation to make a separate build directory. Instead of running cmake and make from within the main freeorion directory, make a build directory (then you also have to add a link to the content directory). if you add it within the freeorion directory you'd want to add it to your .gitignore, but some some folks (but not all it seems) it works to add it outside the freeorion directory. That's probably best to try first. So if you had the source at programs/freeorion, then you would
cd programs
mkdir freeorion.build
cd freeorion.build
ln -s ../freeorion/default .
cmake ../freeorion
make
when you update only the "make" step normally needs to be redone
If you still have trouble with VersionString, then do the same as above but make the build directory be within the freeorion directory (and then the cmake step would be "cmake .." and the link step would be "ln -s ../default ."
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
Also you might want to add "-jx" to the make command if you have multiple cores and/or CPU's, replace the x with the number of cores or number of cores+1. This can speed up compiling by using multiple threads, so say if you have a quad core it would look like: