User:Callahanp: Difference between revisions

Jump to navigation Jump to search
m
Line 17: Line 17:


[[https://github.com/c172p-team/c172p C172P Team on Github ]]
[[https://github.com/c172p-team/c172p C172P Team on Github ]]
 
=== Development Operations ===
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.
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.


Line 40: Line 40:
#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.
#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
==== Part 1 - Creating a Sourceforge Fork ====
 
===== Part 1A - Create a Sourceforge Account, SSH Key and Verify that it works =====
** Requires one personal sourceforge account
** Requires one personal sourceforge account
** ssh login
** Requires an ssh login be setup
*** Create an SSH Key for use with Sourceforge
*** Create an SSH Key for use with Sourceforge
*** Update Sourceforge SSH Keys
*** Update Sourceforge SSH Keys
*** Login to the shell with your key
*** Login to the shell with your key to make sure things are working right.
*** Logout from the shell - You won't be working there.
*** Login to Sourceforge on the web.  You will be working with the web interface to sourceforge to create Forks.
 
===== Part 1B - Create Sourceforge Forks for each Flightgear git repository you need to work in =====
 
If you are not going to make changes to a particular repository, but only wish to build, or just use it, you only need a clone of the official Flightgear on your local machine.  You don't need to bother with creating a SourceForge Fork.
 
Note that if you later decide to contribute to a new area, you will be able to create a fork and attach it to the local clone you previously created using the steps below.
 
* Open https://sourceforge.net/projects/flightgear/
* Log in to your sourceforge account by clicking the login button if you're logged out.
* Hover over Me and select Profile with a right click and select open link in new window.
 
If you don't see Git under personal tools in your profile page, it's because you've not set up any SourceForge Forks yet.


* Create a local fork for each Sourceforge Fork
* Create a local clone for each Sourceforge Fork
** create origin remote
** create origin remote
** create upstream remote
** create upstream remote
936

edits

Navigation menu