config/kernel/bare-metal.in
| author |
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> |
|
Fri Apr 15 00:22:42 2011 +0200 (2011-04-15) |
| changeset 2544 |
751c3f735ada |
| parent 1030 |
e5bf882d6514
|
| permissions |
-rw-r--r-- |
scripts/internals: do not remove lib{32,64}/ symlinks after build
During the build, we create lib{32,64}/ symlinks out of the sysroot.
In some cases (eg. mingw32 target), these symlinks are still required
when running the toolchain. For other combinations, the symlinks are
without incidence, so they can be safely kept after the build.
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?!?!...
|