A versatile (cross-)toolchain generator.
Go to file
Yann E. MORIN" 200c8a2c91 [cc-gcc] Add latest versions
Add gcc-4.4.1
2009-08-02 23:33:38 +02:00
config [cc-gcc] Add latest versions 2009-08-02 23:33:38 +02:00
contrib Update the OpenRISC or32 contrib to correctly set EXPERIMENTAL. 2008-10-15 08:15:28 +00:00
docs [populate] enhance documentation 2009-06-14 21:44:33 +02:00
kconfig Under Cygwin, executables have the .exe suffix: 2009-03-09 22:01:59 +00:00
licenses.d Rename directory "licenses" to "licenses.d" for those filesystems unable to handle lower/upper case. 2007-03-11 09:46:22 +00:00
patches [comp-lib-gmp] Add latest versions 2009-08-02 23:33:37 +02:00
samples [samples] Add a linux -> mingw32 -> i686-linux canadian sample 2009-06-26 19:09:22 +02:00
scripts [scripts-add-version] Handle gcc 4.4+ 2009-08-02 23:33:38 +02:00
.hgignore Add .hgignore file. 2009-06-17 15:27:55 +02:00
.hgtags update tags 2009-06-14 18:19:22 +00:00
.version [configure] Use hg to compute the version string 2009-06-17 10:46:28 +02:00
configure Make it build again for non-local use. 2009-07-15 09:22:47 +02:00
COPYING Update and clarify COPYING (plus a typo). 2008-09-14 18:20:03 +00:00
ct-ng.comp Add a new action: show-tuple 2009-05-13 18:10:47 +00:00
ct-ng.in Add a new action: show-tuple 2009-05-13 18:10:47 +00:00
LICENSES Add the full crosstool-NG sources to the new repository of its own. 2007-02-24 11:00:05 +00:00
Makefile.in ./configure: 2009-05-13 21:32:48 +00:00
README /trunk: 2009-05-21 13:49:15 +00:00
steps.mk /devel/gcc-4.4: 2009-05-25 18:22:26 +00:00
TODO /devel/gcc-4.4: 2009-06-02 21:34:26 +00:00

This is the README for crosstool-NG

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/dokuwiki/projects/crosstool

If you want to enhance crosstool-NG, there's a to-do list in the TODO file.

If you need to send a bug report or a patch, please send a mail with subject
prefixed with "[CT_NG]" with the following destinations:
    TO: yann.morin.1998 (at) anciens.enib.fr
    CC: crossgcc (at) sourceware.org

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.

The people that helped are listed in docs/CREDITS. Many thanks to them! :-)

The list of known issues is listed in docs/known-issues.txt.

Aloha!