1 This is the README for crosstool-NG
17 To get you started, just enter:
20 You can find a (terse and WIP) documentation in docs/overview.txt.
22 You can also point your browser to
23 http://ymorin.is-a-geek.org/projects/crosstool
32 If you need to send a bug report, please send a mail with subject
33 prefixed with "[CT_NG]" with to following destinations:
34 TO: yann.morin.1998 (at) anciens.enib.fr
35 CC: crossgcc (at) sourceware.org
40 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
42 Patches should come with the appropriate SoB line. A SoB line is typically
44 Signed-off-by: John DOE <john.doe@somewhere.net>
46 The SoB line is clearly described in Documentation/SubmittingPatches , section
47 12, of your favourite Linux kernel source tree.
49 Then you'll need to correctly configure Mercurial. There are two extensions
50 that you may find usefull:
51 - mq : http://mercurial.selenic.com/wiki/MqExtension
52 - patchbomb : http://mercurial.selenic.com/wiki/PatchbombExtension
54 Commit messages should look like (without leading pipes):
55 |component: short, one-line description
57 |optional longer description
58 |on multiple lines if needed
60 Here is an example commit message (see revision a53a5e1d61db):
61 |comp-libs/cloog: fix building
63 |For CLooG/PPL 0.15.3, the directory name was simply cloog-ppl.
64 |For any later versions, the directory name does have the version, such as
67 Here's a typical hacking session:
68 hg clone http://ymorin.is-a-geek.org/hg/crosstool-ng crosstool-ng
71 hg qnew -D -U -e my_first_patch
72 *edit patch description*
73 *hack* *hack* *check* *fails* *hack* *hack* *check* *works*
75 *edit patch description, serving as commit message*
76 hg qnew -D -U -e my_second_patch
77 *edit patch description*
78 *hack* *hack* *check* *fails* *hack* *hack* *check* *works*
80 *edit patch description, serving as commit message*
81 hg email --outgoing --intro \
82 --from '"Your Full NAME" <your.email (at) your.domain>' \
83 --to '"Yann E. MORIN" <yann.morin.1998 (at) anciens.enib.fr>' \
84 --cc 'crossgcc (at) sourceware.org'
85 *edit introductory message*
87 *re-send if no answer for a few days*
89 Note: replace' (at) ' above with a plain '@'.
95 The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
101 The list of known issues is listed in docs/known-issues.txt.