kuijfe09 and other users have reported similar issues, and I do remember seeing the same issue during the last release cycle(s) - I am currently trying to reproduce it, apparently fgdata master is pointing to 2.12 already, while SG/FG git next are still looking for 2.11 for some people (even with a full rebuild after deleting the source trees), it doesn't seem to be a local issue, I have seen users report this regardless of OS and/or scripted builds.
It seems to happen during the end of the release cycle when the version file is touched in $FG_ROOT, and when the next branches in SG/FG are set up for the release. Possibly, we may need to augment the git section in the release plan to keep these issues in mind.
Obviously, it doesn't affect people who explicitly set up tracking branches, but it seems to break setups that directly build from next and which directly check out master. I think even daveculp reported the same issue a while ago, and he's a core developer - so there probably is a real issue here, which we need to look into to understand what's going on:
Subject: download_and_compile - can't find osg libsdaveculp wrote:When fgfs tried to start, it quit with a warning that data version 2.8.0 was needed, whereas I only had 2.10.0. I did the simple fix of changing the version number in data to 2.8.0, so fgfs is happy now, however I get a console message that fgfs is operating in a 2.8.0 backward compatibility mode. That doesn't sound good. Any idea what the proper solution is?
@anybody affected by this: please try to delete the cmake cache, and if that doesn't help the whole build tree (or start afresh in a 2nd build tree for SG and FG) and report back.