diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/overview.txt | 92 |
1 files changed, 77 insertions, 15 deletions
diff --git a/docs/overview.txt b/docs/overview.txt index 61b4cba..6cd7726 100644 --- a/docs/overview.txt +++ b/docs/overview.txt @@ -30,6 +30,9 @@ Using the toolchain The 'populate' script Toolchain types Seemingly-native toolchains +Contributing + Sending a bug report + Sending patches Internals Makefile front-end Kconfig parser @@ -123,7 +126,7 @@ There are two ways you can use crosstool-NG: The former should be used if you got crosstool-NG from a packaged tarball, see "Install method", below, while the latter is most useful for developpers that -checked the code out from SVN, and want to submit patches, see "The Hacker's +use a clone of the repository, and want to submit patches, see "The Hacker's way", below. Install method | @@ -157,8 +160,7 @@ Stay in the directory holding the sources, and run: See below for complete usage. Now, provided you used a clone of the repository, you can send me your changes. -See the file README, at the top of crosstool-NG source, for how to submit -changees. +See the section titled CONTRIBUTING, below, for how to submit changees. Preparing for packaging | ------------------------+ @@ -188,18 +190,10 @@ Contributed code | -----------------+ Some people contibuted code that couldn't get merged for various reasons. This -code is available as patches in the contrib/ sub-directory. These patches are -to be applied to the source of crosstool-NG, prior to installing. - -An easy way to use contributed code is to pass the --with-contrib= option to -./configure. The possible values depend upon which contributions are packaged -with your version, but you can get with it with passing one of those two -special values: - --with-contrib=list - will list all available contributions - - --with-contrib=all - will select all avalaible contributions +code is available as lzma-compressed patches, in the contrib/ sub-directory. +These patches are to be applied to the source of crosstool-NG, prior to +installing, using something like the following: + lzcat contrib/foobar.patch.lzma |patch -p1 There is no guarantee that a particuliar contribution applies to the current version of crosstool-ng, or that it will work at all. Use contributions at @@ -605,6 +599,74 @@ used by the cross-compiler it is going to build. The problem seems to arise only with glibc (and eglibc?) starting with version 2.7. +________________ + / +Contributing / +_____________/ + +Sending a bug report | +---------------------+ + +If you need to send a bug report, please send a mail with subject +prefixed with "[CT_NG]" with to following destinations: + TO: yann.morin.1998 (at) anciens.enib.fr + CC: crossgcc (at) sourceware.org + +Sending patches | +----------------+ + +If you want to enhance crosstool-NG, there's a to-do list in the TODO file. + +Patches should come with the appropriate SoB line. A SoB line is typically +something like: + Signed-off-by: John DOE <john.doe@somewhere.net> + +The SoB line is clearly described in Documentation/SubmittingPatches , section +12, of your favourite Linux kernel source tree. + +Then you'll need to correctly configure Mercurial. There are two extensions +that you may find usefull: + - mq : http://mercurial.selenic.com/wiki/MqExtension + - patchbomb : http://mercurial.selenic.com/wiki/PatchbombExtension + +Commit messages should look like (without leading pipes): + |component: short, one-line description + | + |optional longer description + |on multiple lines if needed + +Here is an example commit message (see revision a53a5e1d61db): + |comp-libs/cloog: fix building + | + |For CLooG/PPL 0.15.3, the directory name was simply cloog-ppl. + |For any later versions, the directory name does have the version, such as + |cloog-ppl-0.15.4. + +Here's a typical hacking session: + hg clone http://ymorin.is-a-geek.org/hg/crosstool-ng crosstool-ng + cd crosstool-ng + hg qinit + hg qnew -D -U -e my_first_patch + *edit patch description* + *hack* *hack* *check* *fails* *hack* *hack* *check* *works* + hg qref -D -e + *edit patch description, serving as commit message* + hg qnew -D -U -e my_second_patch + *edit patch description* + *hack* *hack* *check* *fails* *hack* *hack* *check* *works* + hg qref -D -e + *edit patch description, serving as commit message* + hg email --outgoing --intro \ + --from '"Your Full NAME" <your.email (at) your.domain>' \ + --to '"Yann E. MORIN" <yann.morin.1998 (at) anciens.enib.fr>' \ + --cc 'crossgcc (at) sourceware.org' + *edit introductory message* + *wait for feedback* + *re-send if no answer for a few days* + +Note: replace '(at)' above with a plain '@'. + + _____________ / Internals / |