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: acxz
Last Packager: acxz
Votes: 48
Popularity: 0.23
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 »

kerentin commented on 2020-04-26 16:49 (UTC) (edited on 2020-04-26 16:50 (UTC) by kerentin)

Did anyone else get the error

simgear/src/simgear-2019.1.1/simgear/canvas/elements/CanvasText.cxx:351:74: error: passing 'const simgear::canvas::Text::TextOSG' as 'this' argument discards qualifiers [-fpermissive]
  351 |     osgText::Font* activefont = const_cast<osgText::Font*>(getActiveFont());
      |                                                                          ^
In file included from simgear/src/simgear-2019.1.1/simgear/canvas/elements/CanvasText.hxx:24,
                 from simgear/src/simgear-2019.1.1/simgear/canvas/elements/CanvasText.cxx:22:
/usr/include/osgText/Text:267:11: note:   in call to 'osgText::Font* osgText::Text::getActiveFont()'
  267 |     Font* getActiveFont();
      |           ^~~~~~~~~~~~~
make[2]: *** [simgear/CMakeFiles/SimGearScene.dir/build.make:291: simgear/CMakeFiles/SimGearScene.dir/canvas/elements/CanvasText.cxx.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:950: simgear/CMakeFiles/SimGearScene.dir/all] Error 2
make: *** [Makefile:172: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error: target not found: simgear

and know how to solve it?

Potomac commented on 2020-04-16 03:14 (UTC) (edited on 2020-04-16 03:15 (UTC) by Potomac)

@mollitz : I see you use trizen for building and installing AUR package, I suggest to build and install the flightgear package without using trizen, just use the command "makepkg -cf" inside a directory where the PKGBUILD file of flightgear is present,

then install the package with the command : "pacman -U <path to the package>"

perhaps it's a bug in trizen software, something related to a corrupt cache, temporary files used by trizen

mollitz commented on 2020-04-15 18:53 (UTC)

@Potomac, tahnks for the reply. installing openscenegraph and simgear is not the problem. The issue is that for some reason wants to link libpthreads, although I only have libpthread (without s on my system).

"/tmp/trizen-moritz/flightgear/src/flightgear-2019.1.1/CMakeFiles/CMakeError.log" yields the following:

/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2f5bb.dir/link.txt --verbose=1
/usr/sbin/cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-O1,--sort-common,--as needed,-z,relro,-z,now  -rdynamic CMakeFiles/cmTC_2f5bb.di /CheckFunctionExists.c.o  -o cmTC_2f5bb  -lpthreads 
 /usr/sbin/ld: cannot find -lpthreads

I however can't find out why

prescott commented on 2020-04-12 18:42 (UTC) (edited on 2020-04-12 18:47 (UTC) by prescott)

It would be great to have immediately after installation a shortcut with enabled launcher. It is practical for every user...

Shortcut with Launcher: fgfs --launcher --fg-root=/usr/share/flightgear/data

Potomac commented on 2020-04-08 21:01 (UTC) (edited on 2020-04-08 21:04 (UTC) by Potomac)

@mollitz : it should work, check if you have installed all dependencies for flightgear and simgear,

first you have to install openscenegraph 3.6.5 package (last version), then simgear package with this modified PKGBUILD :

https://aur.archlinux.org/packages/simgear/#comment-738074

don't compile directly the source code, just use "makepkg -cf" command and the appropriate PKGBUILD files.

drfunjohn commented on 2020-03-23 09:57 (UTC) (edited on 2020-03-23 11:04 (UTC) by drfunjohn)

FG 2019.1.1 crashes at start after click on the "Fly" button.

  • OSG version 3.6.3
  • kernel 5.5.9-arch1-2
 /usr/lib/libc.so.6 : ()+0x3bd70
  fgfs : osgUtil::StateGraph::~StateGraph()+0x59
  /usr/lib/libosgUtil.so.158 : osgUtil::StateGraph::prune()+0xcd
  /usr/lib/libosgUtil.so.158 : osgUtil::StateGraph::prune()+0x2d
  /usr/lib/libosgUtil.so.158 : osgUtil::StateGraph::prune()+0x2d
  /usr/lib/libosgUtil.so.158 : osgUtil::StateGraph::prune()+0x2d
  /usr/lib/libosgUtil.so.158 : osgUtil::CullVisitor::apply(osg::Camera&)+0x81e
  fgfs : osg::Camera::accept(osg::NodeVisitor&)+0x78
  /usr/lib/libosg.so.158 : osg::Group::traverse(osg::NodeVisitor&)+0x33
  /usr/lib/libosgUtil.so.158 : osgUtil::CullVisitor::apply(osg::Group&)+0xbc
  fgfs : osg::Group::accept(osg::NodeVisitor&)+0x87
  /usr/lib/libosg.so.158 : osg::Group::traverse(osg::NodeVisitor&)+0x33
  /usr/lib/libosgUtil.so.158 : osgUtil::SceneView::cullStage(osg::Matrixd const&, osg::Matrixd const&, osgUtil::CullVisitor*, osgUtil::StateGraph*, osgUtil::RenderStage*, osg::Viewport*)+0x14ac
  /usr/lib/libosgUtil.so.158 : osgUtil::SceneView::cull()+0x4fa
  /usr/lib/libosgViewer.so.158 : osgViewer::Renderer::cull_draw()+0x1f6
  /usr/lib/libosg.so.158 : osg::GraphicsContext::runOperations()+0x189
  /usr/lib/libosgViewer.so.158 : osgViewer::ViewerBase::renderingTraversals()+0x1dc4
  fgfs : fgOSMainLoop()+0x157
  fgfs : fgMainInit(int, char**)+0x1532
  fgfs : main()+0x19f
  /usr/lib/libc.so.6 : __libc_start_main()+0xf3
  fgfs : _start()+0x2e
Aborted (core dumped)

with OSG 3.6.4 and 3.6.5 it does not work (of cause, each time FG should be recompiled). see here from FG forum.

  • With OSG 3.6.4 even application screen does not appears.
  • With OSG 3.6.5 compilation of FG does not pass.

Thanx.

acxz commented on 2020-01-18 03:20 (UTC) (edited on 2020-01-18 03:24 (UTC) by acxz)

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

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 ?

https://pypi.org/project/JSBSim/

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.