936
edits
mNo edit summary |
|||
Line 18: | Line 18: | ||
[[https://github.com/c172p-team/c172p C172P Team on Github ]] | [[https://github.com/c172p-team/c172p C172P Team on Github ]] | ||
I am making an effort to define and show examples of development operations for various parts of Flightgear Code and Data including all SourceForge Git repositories, Scenery, Aircraft, Aircraft Hangars, Airport Data. Add-Ons and anything else that can be used with Flightgear. | |||
FGData | |||
SimGear | |||
FlightGear | |||
FGMeta | |||
GetStart | |||
MacLauncher | |||
OpenRadar | |||
SceneryWeb | |||
TerraGear | |||
Windows 3rdPartyDeps | |||
tarrafs | |||
navdata | |||
pipline | |||
mpmap.js | |||
I will be starting with the steps needed to create and maintain a personal Sourceforge Fork of the main repositories, with a local fork that can be used to work with the next branch or with feature branches on either one of the personal forks or on the personal fork of another contributor, or git bisect operations. | |||
Then I'll be looking at the steps needed to do a build in Release, ReleaseWithDebInfo or Debug variants using the currently checked out branches or commits. We'll also examine git stash operations to preserve work on a feature branch, while bringing next up to date. | |||
Next I'll take a look at debug sessions including gdb at the command line, gdb in gdbgui, and possibly alternative editors like atom and visual studio code. | |||
* Creating a SourceForge fork | |||
** Requires one personal sourceforge account | |||
** ssh login | |||
*** Create an SSH Key for use with Sourceforge | |||
*** Update Sourceforge SSH Keys | |||
*** Login to the shell with your key | |||
* Create a local fork for each Sourceforge Fork | |||
** create origin remote | |||
** create upstream remote | |||
** set upstream fetch to main flightgear repositories | |||
** create a branch for working on changes | |||
** checkout next | |||
** checkout a change branch | |||
** stash changes on a branch | |||
** push a change branch to your SourceForge fork | |||
** pull changes from next | |||
** got fetch | |||
==== Tools ==== | ==== Tools ==== | ||
Line 26: | Line 67: | ||
[[User:Callahanp/Flightgear_and_Simgear_Code/From_Command_Line_to_Holding_Short|From Command Line to Holding Short]]. A look at what gets called when you start Flightgear from the command line until you are on the runway. This is a work in progress, somewhat stalled after Eduard Auvergne's initial work on subsystems. It needs a re-vamp to make it current and publishable. | [[User:Callahanp/Flightgear_and_Simgear_Code/From_Command_Line_to_Holding_Short|From Command Line to Holding Short]]. A look at what gets called when you start Flightgear from the command line until you are on the runway. This is a work in progress, somewhat stalled after Eduard Auvergne's initial work on subsystems. It needs a re-vamp to make it current and publishable. | ||
===== RTFM ===== | ===== RTFM ===== |
edits