Kconfig: Root Kconfig is per architecture
Follow linux kernel style and have root Kconfig be arch specific. Change-Id: Ic0cfbd91b532b4ac7faa12ed23aebc7ae9f054b8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif
parent
89d50ec95a
commit
ba3503621e
141
Kconfig
141
Kconfig
|
|
@ -29,142 +29,11 @@
|
|||
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
# POSSIBILITY OF SUCH DAMAGE.
|
||||
#
|
||||
mainmenu "Tiny Mountain/$SRCARCH Configuration"
|
||||
|
||||
mainmenu "Tiny Mountain Build Options"
|
||||
config SRCARCH
|
||||
string
|
||||
option env="SRCARCH"
|
||||
|
||||
source "kernel/Kconfig"
|
||||
source "arch/$SRCARCH/Kconfig"
|
||||
|
||||
source "misc/Kconfig"
|
||||
|
||||
source "arch/Kconfig"
|
||||
|
||||
menu "General Setup"
|
||||
|
||||
config CROSS_COMPILE
|
||||
string "Cross-compiler tool prefix"
|
||||
help
|
||||
Same as running 'make CROSS_COMPILE=prefix-' but stored for
|
||||
default make runs in this kernel build directory. You don't
|
||||
need to set this unless you want the configured kernel build
|
||||
directory to select the cross-compiler automatically.
|
||||
|
||||
config MINIMAL_LIBC
|
||||
bool
|
||||
prompt "Build minimal c library"
|
||||
default y
|
||||
depends on !NEWLIB
|
||||
help
|
||||
Build integrated minimal c library.
|
||||
|
||||
config TOOLCHAIN_NEWLIB
|
||||
bool
|
||||
prompt "Build with newlib c library"
|
||||
depends on !MINIMAL_LIBC
|
||||
default n
|
||||
help
|
||||
Build with newlib library. The newlib library is expected to be
|
||||
part of the SDK in this case.
|
||||
endmenu
|
||||
|
||||
menu "Debugging Options"
|
||||
|
||||
config STDOUT_CONSOLE
|
||||
bool
|
||||
prompt "Send stdout to console"
|
||||
default n
|
||||
help
|
||||
This option directs standard output (e.g. printf) to the console
|
||||
device, rather than suppressing in entirely.
|
||||
|
||||
config ASSERT
|
||||
bool
|
||||
prompt "Enable __ASSERT() macro"
|
||||
default n
|
||||
help
|
||||
This enables the __ASSERT() macro in the kernel code. If an assertion
|
||||
fails, the calling thread is put on an infinite tight loop. Since
|
||||
enabling this adds a significant footprint, it should only be enabled
|
||||
in a non-production system.
|
||||
|
||||
config ASSERT_LEVEL
|
||||
int
|
||||
prompt "__ASSERT() level"
|
||||
default 1
|
||||
depends on ASSERT
|
||||
help
|
||||
This option specifies the assertion level used by the __ASSERT()
|
||||
macro. It can be set to one of three possible values:
|
||||
|
||||
Level 0: off
|
||||
Level 1: on + warning in every file that includes __assert.h
|
||||
Level 2: on + no warning
|
||||
|
||||
endmenu
|
||||
|
||||
menu "System Monitoring Options"
|
||||
|
||||
|
||||
config PERFORMANCE_METRICS
|
||||
bool
|
||||
prompt "Enable performance metrics"
|
||||
default n
|
||||
depends on EXPERIMENTAL
|
||||
help
|
||||
Enable Performance Metrics.
|
||||
|
||||
config BOOT_TIME_MEASUREMENT
|
||||
bool
|
||||
prompt "Boot time measurements [EXPERIMENTAL]"
|
||||
default n
|
||||
depends on EXPERIMENTAL && PERFORMANCE_METRICS
|
||||
help
|
||||
This option enables the recording of timestamps during system start
|
||||
up. The global variable __start_tsc records the time kernel begins
|
||||
executing, while __main_tsc records when main() begins executing,
|
||||
and __idle_tsc records when the CPU becomes idle. All values are
|
||||
recorded in terms of CPU clock cycles since system reset.
|
||||
|
||||
config CPU_CLOCK_FREQ_MHZ
|
||||
int
|
||||
prompt "CPU CLock Frequency in MHz"
|
||||
default 20
|
||||
depends on BOOT_TIME_MEASUREMENT
|
||||
help
|
||||
This option specifies the CPU Clock Frequency in MHz in order to
|
||||
convert Intel RDTSC timestamp to microseconds.
|
||||
|
||||
endmenu
|
||||
|
||||
menu "Compile and Link Features"
|
||||
|
||||
config COMPILER_OPT
|
||||
string
|
||||
prompt "Custom compiler options"
|
||||
default ""
|
||||
help
|
||||
This option is a free-form string that is passed to the compiler
|
||||
when building all parts of a project (i.e. kernel, LKMs, and USAPs).
|
||||
The compiler options specified by this string supplement the
|
||||
pre-defined set of compiler supplied by the build system,
|
||||
and can be used to change compiler optimization, warning and error
|
||||
messages, and so on.
|
||||
|
||||
A given LKM or USAP can override this setting by means of the
|
||||
OVERRIDE_COMPILER_OPT make variable in its Makefile.
|
||||
|
||||
endmenu
|
||||
|
||||
source "net/Kconfig"
|
||||
|
||||
source "drivers/Kconfig"
|
||||
|
||||
config EXPERIMENTAL
|
||||
bool
|
||||
prompt "Experimental Options"
|
||||
default n
|
||||
help
|
||||
This option enables all experimental options in the project.
|
||||
If it is disabled, all options marked as EXPERIMENTAL will
|
||||
be disabled.
|
||||
If it is enabled, all options marked as EXPERIMENTAL will
|
||||
be available for selection.
|
||||
|
|
|
|||
Loading…
Reference in a new issue