Package Details: flightgear 2020.3.19-2

Git Clone URL: https://aur.archlinux.org/flightgear.git (read-only, click to copy)
Package Base: flightgear
Description: An open-source, multi-platform flight simulator
Upstream URL: http://www.flightgear.org/
Licenses: GPL
Submitter: Barthalion
Maintainer: alesar1 (acxz)
Last Packager: acxz
Votes: 48
Popularity: 0.004347
First Submitted: 2018-01-05 16:04 (UTC)
Last Updated: 2023-12-31 02:54 (UTC)

Pinned Comments

acxz commented on 2022-09-07 14:47 (UTC)

Development is on Github: https://github.com/acxz/flightgear-arch Please open issues and PRs there instead of commenting.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

codebling commented on 2020-01-18 02:21 (UTC)

@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 (UTC)

Hey guys, I am running into a problem. I would like to use this package here (https://aur.archlinux.org/packages/python-gym-jsbsim-git/#news). It requires python-jsbsim and optional requires flightgear for visualization. However, when I try to install flightgear, I receive the following error (https://aur.archlinux.org/packages/python-gym-jsbsim-git/#comment-725336):

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 (UTC)

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 (UTC) (edited on 2020-01-02 00:15 (UTC) by Potomac)

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

/usr/lib/cmake/SimGear/SimGearTargets.cmake

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 :

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

Potomac commented on 2020-01-01 16:58 (UTC) (edited on 2020-01-01 17:00 (UTC) by Potomac)

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 (UTC)

@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 (UTC)

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

Potomac commented on 2019-12-30 23:45 (UTC) (edited on 2019-12-30 23:46 (UTC) by Potomac)

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

"/include"

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.

tunaja commented on 2019-12-11 01:59 (UTC) (edited on 2019-12-11 02:00 (UTC) by tunaja)

I did install it. I apologize for not including that earlier. I can try it again tomorrow.

AWhetter commented on 2019-12-11 00:48 (UTC)

It sounds like you might need to install flightgear-data?