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>
Fri Jan 28 22:06:49 2011 +0100 (2011-01-28)
changeset 2284 7ede374110e5
parent 2076 b58109b7b321
child 2563 e17f35b05539
permissions -rw-r--r--
config: add an option not to remove the destination directory

In certain circumstances, removing the destination/installation directory
is a bad idea. For example, when the build environment is already taking
care of sanitising the build tree, and pre-installs stuff in there, it is
a very bad idea to remove the destination directory.

This happens now in buildroot, as the crostool-NG backend now installs the
toolchain in the common host-tools directory, and pre-install there a few
host-utilities (eg. host-automake and host-gawk).

Provide a config knob to turn on/off the removal of the destination
directory, defaulting to 'y' (previous behavior), and forced to 'n' when
used as a backend.

Reported-by: Peter Korsgaard <jacmet@sunsite.dk>
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