config/kernel/bare-metal.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
parent 890 6227df6bbb79
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>
yann@861
     1
# Bare metal config options
yann@861
     2
yann@861
     3
config KERNEL_bare_metal
yann@861
     4
    select BARE_METAL
yann@861
     5
    help
yann@883
     6
      'Bare metal' refers to those programs that run without any kernel.
yann@861
     7
      
yann@861
     8
      You probably want to say 'y' here if you plan to use your compiler
yann@883
     9
      to build bootloaders. It is not yet suitable to build Linux kernels,
yann@883
    10
      though, because the APCI stuff relies on the target C library headers
yann@883
    11
      being available?!?!...