blob: b90d07ec946b41b0b6f4520dbfe9fb8d50963286 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
This is the README for crosstool-NG
TABLE OF CONTENT /
________________/
- GETTING STARTED
- PARTICIPATING
- Sending a bug report
- Sending patches
- CREDITS
- KNOWN ISSUES
GETTING STARTED /
_______________/
To get you started, just enter:
./configure --help
You can find a (terse and WIP) documentation in docs/overview.txt.
You can also point your browser to
http://ymorin.is-a-geek.org/projects/crosstool
PARTICIPATING /
_____________/
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.
CREDITS /
_______/
The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
KNOWN ISSUES /
____________/
The list of known issues is listed in docs/known-issues.txt.
Aloha!
|