Differences between revisions 45 and 46
Revision 45 as of 2012-03-12 23:02:04
Size: 4980
Editor: 62
Comment:
Revision 46 as of 2013-01-23 09:59:19
Size: 5624
Comment: 10 steps guide
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<TableOfContents(1)>>
Line 2: Line 4:

We are constantly looking for new developers who are willing to donate their time to advance GCC.
Line 8: Line 12:
= Basics = = Basics: Contributing to GCC in 10 easy steps =
Line 10: Line 14:
So, you are ready to contribute to GCC. We are constantly looking for new developers who are willing to donate their time to advance GCC.  1. The most important formality that you need to go through: '''Copyright assignment'''.
Line 12: Line 16:
Before you do, however, there is an important formality that you need to go through: '''Copyright assignment'''.     GCC is owned by the [[http://www.fsf.org|Free Software Foundation (FSF)]], as such, all contributors must assign their copyright to the FSF before any of their changes are accepted. The copyright assignment process is described in [[http://gcc.gnu.org/contribute.html#legal|Contributing to GCC]]. (See also [[http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html|copyright papers]] and [[http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright|forms]].)
Line 14: Line 18:
GCC is owned by the [[http://www.fsf.org|Free Software Foundation (FSF)]], as such, all contributors must assign their copyright to the FSF before any of their changes are accepted. The copyright assignment process is described in [[http://gcc.gnu.org/contribute.html|Contributing to GCC]]. (See also [[http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html|copyright papers]] and [[http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright|forms]].)  1. Accessing the sources:
    * SVN: [[http://gcc.gnu.org/svn.html]] [[http://gcc.gnu.org/wiki/SvnHelp]]
    * Git: http://gcc.gnu.org/wiki/GitMirror
Line 16: Line 22:
 1. Building GCC: http://gcc.gnu.org/install/

 1. [[Testing_GCC|Testing GCC]] and [[PerformanceTesting|Compile time and memory utilization testing]]

 1. [[DebuggingGCC|Debugging GCC]]

 1. [[FormattingCodeForGCC|Formatting code for GCC]]

 1. [[GCC_Research|How to communicate with the GCC community effectively]]

 1. [[http://gcc.gnu.org/contribute.html#patches|Submitting patches]]

 1. [[http://gcc.gnu.org/svnwrite.html|Committing patches]]

 1. Profit!

Welcome to the Getting Started section of the GCC Wiki

We are constantly looking for new developers who are willing to donate their time to advance GCC.

This section contains collected information geared towards folks who are new to GCC and may be feeling a bit lost in the barbaric jungles of GCC's source code. Although we are continuously trying to improve GCC's internal modularity and interfaces, the fact remains that GCC is about 20 years old, fairly large and we need to keep it working on the multitude of supported architectures and languages. So, getting to work with GCC can be a challenge.

Everyone is welcome to add links to tutorials, HOWTOs, cheat sheets, etc that may be floating around the net.

Basics: Contributing to GCC in 10 easy steps

  1. The most important formality that you need to go through: Copyright assignment.

  2. Accessing the sources:
  3. Building GCC: http://gcc.gnu.org/install/

  4. Testing GCC and Compile time and memory utilization testing

  5. Debugging GCC

  6. Formatting code for GCC

  7. How to communicate with the GCC community effectively

  8. Submitting patches

  9. Committing patches

  10. Profit!

Tutorials, HOWTOs

Internal documentation

Dealing with the source code

Structure Of GCC

Reporting and correcting bugs

When using Bugzilla, GCC maintainers (those having at least write after approval status to GCC trunk) should preferably use their username@gcc.gnu.org account to log in Bugzilla.

None: GettingStarted (last edited 2017-09-13 11:25:27 by NathanSidwell)