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
31 If you need to send a bug report, please send a mail with subject
32 prefixed with "[CT_NG]" with to following destinations:
33 TO: yann.morin.1998 (at) anciens.enib.fr
34 CC: crossgcc (at) sourceware.org
39 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
41 Patches should come with the appropriate SoB line. A SoB line is typically
43 Signed-off-by: John DOE <john.doe@somewhere.net>
45 The SoB line is clearly described in Documentation/SubmittingPatches , section
46 12, of your favourite Linux kernel source tree.
48 Then you'll need to correctly configure Mercurial. There are two extensions
49 that you may find usefull:
50 - mq : http://mercurial.selenic.com/wiki/MqExtension
51 - patchbomb : http://mercurial.selenic.com/wiki/PatchbombExtension
53 Here's a typical hacking session:
54 hg clone http://ymorin.is-a-geek.org/hg/crosstool-ng crosstool-ng
57 hg qnew -D -U -e my_first_patch
58 *edit patch description*
59 *hack* *hack* *check* *fails* *hack* *hack* *check* *works*
61 *edit patch description, serving as commit message*
62 hg qnew -D -U -e my_second_patch
63 *edit patch description*
64 *hack* *hack* *check* *fails* *hack* *hack* *check* *works*
66 *edit patch description, serving as commit message*
67 hg email --outgoing --intro \
68 --from '"Your Full NAME" <your.email (at) your.domain>' \
69 --to '"Yann E. MORIN" <yann.morin.1998 (at) anciens.enib.fr>' \
70 --cc 'crossgcc (at) sourceware.org'
71 *edit introductory message*
73 *re-send if no answer for a few days*
75 Note: replace' (at) ' above with a plain '@'.
80 The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
85 The list of known issues is listed in docs/known-issues.txt.