Topic: Unable to build - boost errors
kaputtnik |
Posted at: 2019-11-12, 20:46
I am also on archlinux but for me all is fine without adjusting anything.
So from my side there is no boost issue here. Fight simulator for Widelands: |
hessenfarmer |
Posted at: 2019-11-12, 21:17
Hmm. I am not sure about this, but there was a similar issue on the MSYS environment. In some cases the cmake detection does not work properly with our detection algorithm. However I solved this by googleing and trying, but I really didn' have understand this completely. So I believe it is possible to have the issue in some installations and not in others. At least this needs to be investigated I believe. The "fix" applied is to disable one detection path of 2 fighting mechanisms. But not sure about this as well. Top Quote |
kaputtnik |
Posted at: 2019-11-12, 21:36
I wonder about the used versions: The shown version from Tribal-Chief is:
Whereas my version is shown as:
Beside the different revision numbers, the Fight simulator for Widelands: |
kaputtnik |
Posted at: 2019-11-12, 22:03
@Tribal-Chief: Please describe all steps in detail how you get the source code. Fight simulator for Widelands: |
Tino |
Posted at: 2019-11-13, 07:51
https://github.com/widelands/widelands/commit/e209f37cea9cdd8173d0c5a79527cd52f7347b47 Top Quote |
Tribal-Chief Topic Opener |
Posted at: 2019-11-13, 10:05
I followed the instructions on this site. fork widelands/widelands git clone <my fork> run compile script I was assuming this would get me the latest trunk. Top Quote |
hessenfarmer |
Posted at: 2019-11-13, 12:56
It might be that this commit has been overridden by the last commit of Sirver into utils detect_revision.py so at least the differing version description might be explainable. Still we need to find out what might cause the boost issues seen in MSYS and by tribal-chief. Top Quote |
hessenfarmer |
Posted at: 2019-11-13, 13:00
from my perspective this assumption is correct at the time of the fork. Afterwards you need to update the fork with the changes in master. However I beleive this might explain the differing widelands version (see my last post) but not the boost issue. Top Quote |
jmoerschbach |
Posted at: 2019-11-13, 19:55
Did you downgrade boot as mentioned in step 5? I'm on windows using msys with no problems at all following closely all the steps provided in https://www.widelands.org/wiki/BuildingWidelandsUnderWindowsNew/ Top Quote |
Tribal-Chief Topic Opener |
Posted at: 2019-11-13, 22:27
Why would I even look at at windows install, and downgrading boot, or did you mean boost, is not really an option as I need the latest boost for many projects. Top Quote |