A versatile (cross-)toolchain generator.
Go to file
2010-01-31 13:04:34 +01:00
config Backport 1380 from trunk: 2009-02-17 17:08:18 +00:00
contrib Update the OpenRISC or32 contrib to correctly set EXPERIMENTAL. 2008-10-15 08:15:28 +00:00
docs Get rid of the local-test in Makefile. 2008-11-16 22:19:57 +00:00
kconfig Merge 1199 and 1200 from /devel/YEM-build_host_target_cleanup: 2008-11-13 17:55:16 +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 Backport 1305 from /trunk: 2009-01-27 23:26:01 +00:00
samples Update all these samples. 2008-11-25 18:41:49 +00:00
scripts Fix 'extracting' sstrip. Thanks to Michael ABBOTT for spotting this. 2009-02-02 17:22:16 +00:00
tools Make the 'updatetools' rule conform to the V={,0,1,2} verbosity level. 2008-11-13 17:34:44 +00:00
.version Bump version to 1.3.3+svn. 2009-04-02 21:21:15 +00:00
configure Backport 1382 from /trunk: 2009-02-17 21:07:15 +00:00
COPYING Update and clarify COPYING (plus a typo). 2008-09-14 18:20:03 +00:00
ct-ng.comp Remove regtest actions, introduce build-all actions: 2008-10-31 18:31:01 +00:00
ct-ng.in Update help (mostly eye-candy). 2008-10-31 18:29:15 +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 Get rid of the local-test in Makefile. 2008-11-16 22:19:57 +00:00
README Typoes. 2008-10-06 20:13:05 +00:00
steps.mk Build target GMP and MPFR prior to target binutils: 2008-11-04 18:28:56 +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 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

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!