Re: [Flightgear-devel] Hard coded fg-root path in flightgearstartup?

[Florent R. <f.r...@fr...>]

Hi Alan,

"Alan Teeder" <ajt...@v-...> wrote:

> C:/Users/alan/Appdata/Roaming/flightgear.org/    .......  fgfs.log, 

So, this is $FG_HOME/fgfs.log

> autosave.xml, navdataxxx.cache and many other files and directories.

all in $FG_HOME.

> C:/Users/alan/Documents/Flightgear/Aircraft (which is empty!)

This is where aircraft downloaded using the catalog system (doable from
the builtin launcher and previously also from the experimental Aircraft
Center) would go unless you change FG's download dir. This comes from:

options.cxx:

  SGPath defaultDownloadDir()
  {
  #if defined(SG_WINDOWS)
      SGPath p(SGPath::documents());
      p.append("FlightGear");
  #else
      SGPath p(globals->get_fg_home());
  #endif
      return p;
  }

and fg_init.cxx:

  void fgInitPackageRoot()
  {
      if (globals->packageRoot()) {
          return;
      }

      SGPath packageAircraftDir = flightgear::Options::sharedInstance()->valueForOption("download-dir");
      if (packageAircraftDir.isNull()) {
          packageAircraftDir = flightgear::defaultDownloadDir();
      }

      packageAircraftDir.append("Aircraft");

      SG_LOG(SG_GENERAL, SG_INFO, "init package root at:" << packageAircraftDir);


      SGSharedPtr<Root> pkgRoot(new Root(packageAircraftDir, FLIGHTGEAR_VERSION));
      // set the http client later (too early in startup right now)
      globals->setPackageRoot(pkgRoot);

  }

> C:/Users/alan/.fgfsrc

I consider this as legacy, only supported for compatibility. You can use
$FG_HOME/fgfsrc instead, which doesn't start with a dot (cf.
fgInitConfig() in fg_init.cxx and Options::init() in options.cxx).

> C:/Flightgear/fgdata/Joysticks.xml

Mine starts with a lowercase 'j'... Indeed, when someone wants to
customize this one, it's a bit delicate ('git pull --rebase' or StGit
can help, but beware that StGit is unmaintained, AFAIK).

> C:/Flightgear/fgdata/Input/Joysticks/(my joystick files)

Same problem, except you can instead put your customized files in
$FG_HOME/Input/Joysticks, where they will take precedence over those in
FGData. But be sure to take precautions not to lose your files---either
with backups or by marking them read-only---otherwise using the joystick
config dialog in-sim could overwrite them (though just checking the axes
behaviors/values doesn't overwrite any file; I believe you have to change
bindings or something like that).

Regards

P.S.: of course, people unhappy with the paths on Windows are welcome, I
      think, to file merge requests and deal with the migration process.

-- 
Florent