A versatile (cross-)toolchain generator.
Go to file
Anthony Foiani 3555e03268 complibs/ppl: build only C and C++ interfaces for PPL
By default, PPL wants to build interfaces for any of a variety of
langauges it finds on the local host (python, java, possibly perl, also
more esoteric languages such as ocaml and prolog).

These extra interfaces can double the compile time for the library. For
single-process builds, I found a savings of more than 40%:

  default    / j1: 716s total, 143.2s avg, 0.52s stdev
  just_c     / j1: 406s total,  81.2s avg, 0.33s stdev
  just_c_cpp / j1: 413s total,  82.6s avg, 0.22s stdev

And for multi-process builds, it approached 50%:

  default    / j4: 625s total, 125.0s avg, 0.57s stdev
  just_c     / j4: 338s total,  67.6s avg, 1.25s stdev
  just_c_cpp / j4: 327s total,  65.4s avg, 0.36s stdev

Since the PPL we build within ct-ng is only used by GCC, we only need to
build the C and C++ interfaces.

Signed-Off-By: Anthony Foiani <anthony.foiani@gmail.com>
2011-05-19 23:06:16 +02:00
config libc/glibc: source common parts instead of symlinking 2011-05-18 23:48:56 +02:00
contrib testsuite: fix gcc test-suite 2010-11-03 18:36:51 +01:00
docs docs: add a status for know issues 2011-04-07 19:21:15 +02:00
kconfig kconfig: add the nconf frontend 2011-05-12 19:45:30 +02: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 libc/glibc: update patchset, add ports patchset 2011-05-03 00:20:04 +02:00
samples sample: add new Alpha sample with glibc-.13 2011-05-04 19:19:56 +02:00
scripts complibs/ppl: build only C and C++ interfaces for PPL 2011-05-19 23:06:16 +02:00
.hgignore kconfig: add the nconf frontend 2011-05-12 19:45:30 +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 scripts: remove aria2c as downloader, retain only curl and wget 2010-11-16 10:00:27 +01:00
COPYING Update and clarify COPYING (plus a typo). 2008-09-14 18:20:03 +00:00
ct-ng.comp samples: add a short list of all samples 2010-07-30 23:30:02 +02:00
ct-ng.in scripts: leave changelog in build dir, copy to install dir 2011-03-20 00:02:21 +01: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 scripts: fix installation 2011-04-30 23:13:12 +02:00
README docs: review REaDME 2010-08-23 23:24:16 +02:00
steps.mk kernel: move the headers install step 2011-01-22 22:52:57 +01:00
TODO docs/TODO: remove finished items, update descriptions for remaining items 2010-01-13 19:27:12 +01:00

This is the README for crosstool-NG

Crosstool-NG follows the autoconf dance. So, to get you
kick-started, just run:
  ./configure --help

You will find the documentation in the directory 'docs'.
Here is a quick overview of what you'll find there:
  0 - Table of content
  1 - Introduction
  2 - Installing crosstool-NG
  3 - Configuring a toolchain
  4 - Building the toolchain
  5 - Using the toolchain
  6 - Toolchain types
  7 - Contributing
  8 - Internals
  A - Credits
  B - Known issues
  C - Misc. tutorials

You can also point your browser at:
  http://ymorin.is-a-geek.org/projects/crosstool

Aloha!