config/libc/none.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
child 2444 896cb0d36c1a
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # Dummy config file to not use a C library *at all*
     2 # depends on BARE_METAL
     3 
     4 config LIBC_none
     5     help
     6       Do not use a C library.
     7       
     8       This is usefull if your project is self-contained, does not rely on
     9       an external C library, and provides all the necessary bits.
    10       
    11       Most probably usefull to bootloaders, as they generally don't depend
    12       on the C library.
    13       
    14       If unsure: do *not* choose that, and use another option in the choice.