Board index FlightGear Support Compiling

Superbuild on windows using wiki

Building FlightGear from source, and in the need for help?

Superbuild on windows using wiki

Postby jaxsin » Fri Feb 26, 2016 1:50 pm

With the help of hazma, I managed to get the superbuild going on my windows machine using his modified CMAKE file.

My question now I have fginstall folder full of *.exe files and nothing else. So, I then did a quick C&P of the new compiled *.exe files into my FG installation\bin folder. C&P'd the fgdata folder from fgmeta to my FG installation\data folder and then tried to run the cmd
Code: Select all
fgfs.exe --launcher

I just get the default c172p loaded, launcher never shows up
If I try and launch it using the icon, I get a black window with a popup box that says "Required data files not found, check your installation. Looking for base-package files at: '..\data'"

Seems maybe my QT has failed in the compilation process somewhere?
jaxsin
 
Posts: 395
Joined: Mon Dec 28, 2015 3:54 pm

Re: Superbuild on windows using wiki

Postby Hooray » Fri Feb 26, 2016 4:11 pm

you need the base package, i.e. set $fg_root accordingly (see the wiki for details)
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 12090
Joined: Tue Mar 25, 2008 8:40 am

Re: Superbuild on windows using wiki

Postby jaxsin » Sat Feb 27, 2016 1:45 am

Hooray wrote in Fri Feb 26, 2016 4:11 pm:you need the base package, i.e. set $fg_root accordingly (see the wiki for details)


Sure I did this and got the same behavior. This is completely frustrating. How can I get a successful build, copy the *exe files from the build folder to a 2016.2.0 nightly install and end up with this problem? It knows where the root is at because it loads the cessna and KSFO airport just fine. All I am doing is replacing the executible files from my own compilations directory to the FG install.

I am so close to giving up
jaxsin
 
Posts: 395
Joined: Mon Dec 28, 2015 3:54 pm

Re: Superbuild on windows using wiki

Postby wkitty42 » Sat Feb 27, 2016 9:06 pm

don't forget that each version has its own configuration file... i have found files specific to 3.4, 3.5, 3.6, 3.7, 2016.1.0, 2016.1.1, and 2016.2.0 on my system... the fgfs binary creates them with default values when it first starts up... it has caught me out several times when i thought certain settings were in play and they weren't...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 6966
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: Superbuild on windows using wiki

Postby jaxsin » Wed Mar 02, 2016 3:43 pm

ok I figured out what the problem was with the ..\data files while launching the --launcher. Now I can finally see the error that may be causing the --launcher not to load, which then causes fgfs.exe to load with the defaults. I have not applied the latest fix that would stop this default loading behavior when exiting the launcher.

console output
Code: Select all
Enabling ATI viewport hack
Starting automatic scenery download/synchronization. Using built-in SVN support. Directory: 'C:/Users/jasin/Documents/FlightGear/TerraSync'.
canvas::Text: Missing 'ttf' font reader
SVNDirectory::deleteChildByName: failed to remove dir:S at path:
        Path "C:/Users/jasin/Documents/FlightGear/TerraSync/Airports/F/S"
Animated jetways ... initialized
canvas::Text: Failed to open font file D:/flightgear_dev/data/Fonts/LiberationFonts/LiberationSans-Bold.ttf
jaxsin
 
Posts: 395
Joined: Mon Dec 28, 2015 3:54 pm


Return to Compiling

Who is online

Users browsing this forum: No registered users and 1 guest