config/kernel/bare-metal.in
author |
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> |
|
Sat Jan 14 18:22:06 2012 +0100 (2012-01-14) |
changeset 2835 |
0a2fa748727e |
parent 1030 |
e5bf882d6514
|
permissions |
-rw-r--r-- |
kconfig: install compiled frontends
The kconfig frontends are currently instaleld as source files. This is
a remnant of the early times, when I wanted a single installation of
crosstool-NG to be shared across multiple machines, potentially of
different architectures.
This does not really make sense, and it's been a long time since it
was las tpossible in practice.
So, just build the kconfig frontends at make-time, and install them
as we do for all other crosstool-NG dependent files.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@861
|
1 |
# Bare metal config options
|
yann@861
|
2 |
|
yann@2444
|
3 |
## select BARE_METAL
|
yann@2444
|
4 |
##
|
yann@2444
|
5 |
## help 'Bare metal' refers to those programs that run without any kernel.
|
yann@2444
|
6 |
## help
|
yann@2444
|
7 |
## help You probably want to say 'y' here if you plan to use your compiler
|
yann@2444
|
8 |
## help to build bootloaders. It is not yet suitable to build Linux kernels,
|
yann@2444
|
9 |
## help though, because the APCI stuff relies on the target C library headers
|
yann@2444
|
10 |
## help being available?!?!...
|