Board index FlightGear Support Compiling

Can compile 2019.2.0 but not run it (Win10)  Topic is solved

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

Can compile 2019.2.0 but not run it (Win10)

Postby cbgonzalez » Wed Mar 20, 2019 6:22 pm

Hello all,

I´m able to successfully compile FlightGear (+SImGear) on Win 10, VisualStudio Express 2017 (after some small mods to http://wiki.flightgear.org/Building_using_CMake_-_Windows). The build (and install) complete without any error.

When running the executable, though, I get errors re. missing dlls:
CrashRpt1403.dll,
osg131-osgDB.dll,
osg131-osgSim.dll,
osg131-osgText.dll

and the program exits.

The dlls exist where they are supposed to be (according to the wiki doc above) but fgfs is not able to find them.

I´m pretty sure I´m missing some cmake directives but some poking around several dozens of cmake files turned up nothing...

Any pointers from somebody who has compiled successfully?

Thanks in advance,

Cristian.
cbgonzalez
 
Posts: 9
Joined: Tue Jan 29, 2019 4:30 pm

Re: Can compile 2019.2.0 but not run it (Win10)  

Postby xDraconian » Thu Mar 21, 2019 2:23 am

Hi Cristian,

It will search for the DLLs in the current folder or any folders specified in your PATH. Either update your PATH environment variable, or do so via your command file.

e.g.
SET PATH=%ROOT_DIR%/bin;%ROOT_DIR%/../x64-windows/bin;%QT5x64%/bin;%PATH%
fgfs --launcher

Scott
xDraconian
 
Posts: 238
Joined: Sun Jan 21, 2018 5:53 am
Version: Git
OS: Linux Mint

Re: Can compile 2019.2.0 but not run it (Win10)

Postby cbgonzalez » Thu Mar 21, 2019 12:58 pm

Thanks Scott,

Adding the location of Qt and OSg dlls to the PATH works!.

The FG installer does not meddle with the path though, any idea how this works with a distribution package? Just curious.

Thanks again!

Cristian.
cbgonzalez
 
Posts: 9
Joined: Tue Jan 29, 2019 4:30 pm

Re: Can compile 2019.2.0 but not run it (Win10)

Postby xDraconian » Fri Mar 22, 2019 12:09 am

I've always built from source, so I'm not familiar with the approach being taken by the distro packages. My guess would be that the DLLs are being installed to the System folder and thus detectable by Windows' libloader process.
xDraconian
 
Posts: 238
Joined: Sun Jan 21, 2018 5:53 am
Version: Git
OS: Linux Mint


Return to Compiling

Who is online

Users browsing this forum: No registered users and 1 guest