config/libc/none.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Mar 05 09:19:56 2010 +0100 (2010-03-05)
changeset 1842 2535545dd450
child 2444 896cb0d36c1a
permissions -rw-r--r--
config: prepare for build-system backend

When acting as a backend for a build-system, we should not build
any application that runs on the target, that is:
- no native gdb
- no companion libraries
- no binutils libraries
- no debug tools (save for gdbserver)
- ...

Here, we simply prepare the (hidden) config option that will detect
that we are acting as a back-end.

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