mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2024-12-21 13:47:48 +00:00
A versatile (cross-)toolchain generator.
config | ||
contrib | ||
docs | ||
kconfig | ||
licenses.d | ||
patches | ||
samples | ||
scripts | ||
.hgignore | ||
.hgtags | ||
.version | ||
configure | ||
COPYING | ||
ct-ng.comp | ||
ct-ng.in | ||
LICENSES | ||
Makefile.in | ||
README | ||
steps.mk | ||
TODO |
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!