config/kernel/bare-metal.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 890 6227df6bbb79
child 2444 896cb0d36c1a
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
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?!?!...