Board index FlightGear Support

Self built binary, matching installed version, wants datadir  Topic is solved

All general support: help on flying, installation, hardware, getting online etc. There are lots of users and developers to help you out.
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.

- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?
- does the problem occur with any aircraft, at any airport?
- where did you download your aircraft/scenery from?
- is there any output printed to the console (black window)?
- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).

Please report any bugs not specific to an aircraft on the issue tracker.
To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article.

Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.

Self built binary, matching installed version, wants datadir  

Postby property_tree » Mon Oct 31, 2022 4:50 pm

I've been building the binary for the 2020.13 branch 'at home', because it's the version I have installed via my Linux distros package manager script suggestion.
The one built via the script installed and ran perfectly.

But since I have started dabbling in the source code, to fix some things, I built the binary myself, too.
But when I start it, at least from the build/src/main/ directory, it asks me for the data dir once, and then not again.

If I then run the system path binary from my distro, it also doesn't ask it again.
I can then switch between the binaries all day long and none ask me.

Why is that?
Is it normal?
Does it save this information somewhere ( I assume so...) and where is it?
It doesn't seem to be ~/.fgfs, so...yeah.

Edit:
I think I have figured it out.
The system wide installation quite likely has the FG_HOME 'built in'
Wheras the self built one seems to use an 'ini' file entry.
Code: Select all
fg-root-2020-3-13=/usr/share/FlightGear/
property_tree
 
Posts: 98
Joined: Wed Oct 26, 2022 1:13 pm

Return to Support

Who is online

Users browsing this forum: No registered users and 3 guests