You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Yann E. MORIN" 76a9f0fd16 [debug-duma] Add latest versions
Add 2.5.15, propagate patchset from 2_5_14 up to 2_5_15.
14 years ago
config [debug-duma] Add latest versions 14 years ago
contrib Update the OpenRISC or32 contrib to correctly set EXPERIMENTAL. 15 years ago
docs [populate] enhance documentation 15 years ago
kconfig Under Cygwin, executables have the .exe suffix: 15 years ago
licenses.d Rename directory "licenses" to "licenses.d" for those filesystems unable to handle lower/upper case. 17 years ago
patches [debug-duma] Add latest versions 14 years ago
samples [samples] Add a linux -> mingw32 -> i686-linux canadian sample 14 years ago
scripts [samples] Don't mix canadian samples with non-canadian ones. 14 years ago
.hgignore Add .hgignore file. 14 years ago
.hgtags update tags 15 years ago
.version [configure] Use hg to compute the version string 14 years ago
COPYING Update and clarify COPYING (plus a typo). 15 years ago
LICENSES Add the full crosstool-NG sources to the new repository of its own. 17 years ago
Makefile.in ./configure: 15 years ago
README /trunk: 15 years ago
TODO /devel/gcc-4.4: 15 years ago
configure Make it build again for non-local use. 14 years ago
ct-ng.comp Add a new action: show-tuple 15 years ago
ct-ng.in Add a new action: show-tuple 15 years ago
steps.mk /devel/gcc-4.4: 15 years ago

README

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!