User:Texnicer/devblog: Difference between revisions
Line 16: | Line 16: | ||
$ cd /usr/share/games/flightgear/ | $ cd /usr/share/games/flightgear/ | ||
Hence I looked for garmin196 invoking a full recursive file-search | |||
me@machine:/usr/share/games/flightgear/$ ls -R | grep -A1 -i garmin196 | |||
and I figured that the device's files are located in /Aircrafts/Instrument-3d/garmin196 | |||
=== Understanding the components of the system === | === Understanding the components of the system === |
Revision as of 19:46, 25 March 2020
Adding a existing component to an existing aircraft
On march 25, 2020 I was asked via mumble, if I could add the garmin196 to the Seneca II, hence the AP is not charming. Here ist what I did, an how I did it.
Creating a working copy of the aircraft
At first I aquired the Aircraft. It's part of the sourceforge/svn-repository.
I got the plane searching throught FGADDON/AIRCRAFT (https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/) using the SVN system.
$ svn checkout https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/SenecaII
note: sourceforge does not support the correct svn-codeline, you need to correct the path starting after trunk'
Locating the system to add
I went into my system's Flightgear root directory $FG_ROOT - which is nice to know. On ubuntu and DeBIAN systems it is likely to be found in:
/usr/share/games/flightgear
$ cd /usr/share/games/flightgear/
Hence I looked for garmin196 invoking a full recursive file-search
me@machine:/usr/share/games/flightgear/$ ls -R | grep -A1 -i garmin196
and I figured that the device's files are located in /Aircrafts/Instrument-3d/garmin196