Package Details: flightgear 2019.1.1-1

Git Clone URL: (read-only, click to copy)
Package Base: flightgear
Description: An open-source, multi-platform flight simulator
Upstream URL:
Licenses: GPL
Submitter: Barthalion
Maintainer: tim.hellhake
Last Packager: tim.hellhake
Votes: 29
Popularity: 0.68
First Submitted: 2018-01-05 16:04
Last Updated: 2019-12-12 14:19

Latest Comments

1 2 3 4 5 6 Next › Last »

acxz commented on 2020-01-18 03:20

@codebling Thanks for the quick response, yeah I think the best option would be if flightgear packages jsbsim seperately. Another thing they can do is provide a CMake flag for using their package jsbsim or a system installed jsbsim. I'll bring up the issue to upstream.

@Potomac That is a route I can go for my specific problem. But generally, if you want to use the python bindings of jsbsim and flightgear together you cannot at the moment due to this problem. EDIT: NVM you are saying to install python-jsbsim in the venv. I would like to get system level jsbsim python bindings. It should be possible with a bit of work from the flightgear side, if upstream is willing.

Potomac commented on 2020-01-18 03:16

Python modules can be installed on a virtual environment (anaconda, pip), located on the /home of the user

perhaps instead of using a package for python-bsim you can try to install it in a python virtual environment, where the binary jbsim will be built and installed automatically by pip or anaconda ?

codebling commented on 2020-01-18 02:21

@acxz yes it looks like the FlightGear does install/own /usr/bin/JSBSim binary. It uses this for flight dynamics, see the wiki.

I see that you are the creator and owner of the python-gym-jsbsim-git package. I'm not sure what your options are here. I suppose ideally that FlightGear would have a dependency on another JSBSim instead of bundling its own.

acxz commented on 2020-01-18 01:40

Hey guys, I am running into a problem. I would like to use this package here ( It requires python-jsbsim and optional requires flightgear for visualization. However, when I try to install flightgear, I receive the following error (

error: failed to commit transaction (conflicting files)
flightgear: /usr/bin/JSBSim exists in filesystem (owned by python-jsbsim-git)
Errors occurred, no packages were upgraded.

It seems like flightgear is providing its own jsbsim exe? Is there any way to fix this?

codebling commented on 2020-01-02 02:29

Glad you found it! In a fresh install of flightgear + deps (simgear not previously installed), worked out of the box for me. I'm using an AUR helper

Potomac commented on 2020-01-02 00:15

I found the root cause of the problem, it is in this file from simgear package :


inside at line 66 the path "/include" was added by simgear 2019.1 during compilation :

INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include;/include;/usr/include"

removing "/include" path solves my problem :


Potomac commented on 2020-01-01 16:58

A workaround is to create a symbolic link "/include", before trying to compile flightgear 2019.1 :

ln -s /usr/include /include

@codebling : check if you have a symbolic link "/include", it can explain why you don't have the cmake errors during compilation of flightgear

Potomac commented on 2020-01-01 16:57

@codebling : it's not normal, you should have also this error during compilation if all your packages are up to date,

How do you compile with makepkg ? In a clean chroot or in an normal environment ?

Which version of simgear do you have ?

codebling commented on 2020-01-01 01:36

@Potomac, works for me and package hasn't changed

Potomac commented on 2019-12-30 23:45

This package doesn't build, I have errors related to cmake :

-- Configuring done CMake Error in src/GUI/CMakeLists.txt: Imported target "SimGearCore" includes non-existent path


in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:

  • The path was deleted, renamed, or moved to another location.

  • An install or uninstall procedure did not complete successfully.

  • The installation package was faulty and references files it does not provide.