Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
docs/7 - Contributing to crosstool-NG.txt
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Feb 24 22:31:15 2011 +0100 (2011-02-24)
changeset 2320 5f681a2a0a89
parent 2076 b58109b7b321
child 2563 e17f35b05539
permissions -rw-r--r--
docs: add an in-depth explanations of the build steps

The build process is quite complex: gcc is built three times, there are
two C library steps, there are those companion libraries...

People often wonder what all these steps do, and why they are needed.

Recently, someone proposed a tutorial on the crossgcc mailing list:
http://sourceware.org/ml/crossgcc/2011-01/msg00059.html

This meant that there was a need for such a tutorial, and explanations
on how a toolchain is built. So i decide to extend my answers:
http://sourceware.org/ml/crossgcc/2011-01/msg00060.html
http://sourceware.org/ml/crossgcc/2011-01/msg00125.html

into proper documentation in crosstool-NG.

Thanks go to Francesco for suggesting this. He has a fine tutorial
for beginners there:
http://fturco.org/wiki/doku.php?id=debian:cross-compiler

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 File.........: 7 - Contributing to crosstool-NG.txt

     2 Copyrigth....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>

     3 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5

     4 

     5 

     6 Contributing to crosstool-NG  /

     7 _____________________________/

     8 

     9 

    10 Sending a bug report |

    11 ---------------------+

    12 

    13 If you need to send a bug report, please send a mail with subject

    14 prefixed with "[CT_NG]" with to following destinations:

    15     TO: yann.morin.1998 (at) anciens.enib.fr

    16     CC: crossgcc (at) sourceware.org

    17 

    18 

    19 Sending patches |

    20 ----------------+

    21 

    22 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.

    23 

    24 Patches should come with the appropriate SoB line. A SoB line is typically

    25 something like:

    26    Signed-off-by: John DOE <john.doe@somewhere.net>

    27 

    28 The SoB line is clearly described in Documentation/SubmittingPatches , section

    29 12, of your favourite Linux kernel source tree.

    30 

    31 

    32 For larger or more frequent contributions, mercurial should be used.

    33 There is a nice, complete and step-by-step tutorial in section 'C'.
crosstool-ng