Re: [Flightgear-devel] Compiling Flightgear on Ubuntu

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

Ron Haertel <gs6...@gm...> wrote:

> I just created a new system (old computer) with ubuntu 18.04.2 LTS.  I
> installed the OS and wiped out the previous windows OS.
>
> Using parts of the wiki article:
>
> http://wiki.flightgear.org/index.php?title=Scripted_Compilation_on_Linux_Debian/Ubuntu&mobileaction=toggle_view_desktop

This article is outdated. Authoritative current documentation is:
  - the output of 'download_and_compile.sh --help';
  - what I wrote on this list;
  - the wiki page at [1];
  - stuff written by rominet on <http://fr.flightgear.org/>.

> wget -O download_and_compile.sh (...)

I'd rather sugest you do as I described in [2], namely:

,----
|   cd <dir of your choice>
|   git clone https://git.code.sf.net/p/flightgear/fgmeta
| 
| After a few seconds (minutes if your connection is “slow”), you'll have
| it in the 'fgmeta' directory created by the 'git clone' command.
| 
| Whenever you want to update it (assuming you didn't modify the script):
| 
|   cd fgmeta && git pull
`----

This way:
  - 'download_and_compile.sh --version' will work;
  - it's easier to update it and browse through the changes
    (cd fgmeta && git log -- download_and_compile.sh)

If you *really* want to modify the script (which I discourage:
command-line options are there to avoid this need, and updates are much
more time-consuming and error-prone when you have to apply your own
changes manually), the easiest way is to add them to your FGMeta clone
in the form of one or more commits (no need to push them anywhere,
commits can remain in your clone). Make sure your FGMeta repo is clean
(use 'git status'). Then you can update it with:

  # --rebase will apply your commits on top of the latest repo state
  cd fgmeta && git pull --rebase

If your changes conflict with the update, Git will tell you and you'll
have to resolve the conflict manually (look for “Git resolve conflict”
on your favorite search engine)... or start again from a pristine FGMeta
clone.

> I had to change the https to git for fgdata - getting the common error
> others get.
>
> change lines 380-382
>
> # These are the default values but may be overridden via command-line options.
> REPO_DEFAULT_PROTO='https'
> REPO_DEFAULT_USERNAME=''
>
>
> Change https to git.

Eeeeeek, why do you think I wrote [3]? The protocol used when you put
'git://' is neither authenticated nor encrypted; you can't be sure of
what you're downloading and then running...

> I used ./download_and_compile.sh
> to run the script - no other parameters, as this will download all the
> other libs FG needs.

Right.

> After that if any updates from next are needed I run the script
> ./download_and_compile.sh -p n

Right.

> I also changed the line 380 back to https.

Eeeek!

> To get the QT launcher to work I also add:
>
>             -DENABLE_FLITE=ON \
>                            -DENABLE_QT=1 \
>             -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR_FGFS" \
>
>
> between lines 898 and 899

? Everyone I know using the script already gets the Qt launcher properly
built, AFAIK. Qt is autodetected when the packages are there, and they
should be.

Besides, I'd avoid modifying run_fgfs.sh: this creates another
repetitive change you have to do all the time. Rather, either:

  (a) create your own script that calls run_fgfs.sh with the --launcher
      argument:

------------------------------------------------------------------------
#! /bin/sh

/path/to/run_fgfs.sh --launcher
------------------------------------------------------------------------

or

  (b) create a shell alias (syntax valid for Bash and Zsh):

      alias my-fgfs="/path/to/run_fgfs.sh --launcher"

or

  (c) create a shell function that does the same:

------------------------------------------------------------------------
my-fgfs() {
    /path/to/run_fgfs.sh --launcher
}
------------------------------------------------------------------------

For aliases and shell functions to be installed permanently, you have to
put them in particular files loaded by your shell when it is started
(otherwise they vanish when you close the shell). I use Zsh and put
aliases and short shell functions in ~/.zshrc. If you use another shell,
use the script solution (see (a) above) or ask your favorite search
engine where to install aliases or shell functions ([4] may help
concerning aliases in Bash). Once you've modified the relevant files
(such as ~/.zshrc or ~/.bashrc), start a new shell or run:

  exec "$SHELL"

otherwise your new aliases or shell functions won't be loaded into your
working shell yet (they are loaded whenever you *execute* the commands
in (b) or (c), either manually for testing or via startup files of
your shell such as ~/.zshrc and ~/.bashrc).

Regards

[1] http://wiki.flightgear.org/User:Rominet
[2] https://sourceforge.net/p/flightgear/mailman/message/36634358/
[3] https://sourceforge.net/p/flightgear/mailman/message/36633375/
[4] https://askubuntu.com/questions/17536/how-do-i-create-a-permanent-bash-alias/17537#17537

-- 
Florent