Some scenarios like initial bootloaders do not need interactive shell support, so make this optional. Without a shell a board must provide its own run_shell function. Signed-off-by: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> --- common/Kconfig | 13 ++++++++++++- 1 files changed, 12 insertions(+), 1 deletions(-) diff --git a/common/Kconfig b/common/Kconfig index 83975ee..c3449a9 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -37,6 +37,9 @@ config BLOCK config BLOCK_WRITE bool +config HAVE_NOSHELL + bool + menu "General Settings " config LOCALVERSION_AUTO @@ -234,6 +237,14 @@ choice select COMMAND_SUPPORT help simple shell. No if/then, no return values from commands, no loops + + config SHELL_NONE + depends on HAVE_NOSHELL + bool "no shell (noninteractive build)" + help + No shell at all. This means no shell is started and your board has + to provide a run_shell() function which is started at the end of + the barebox startup process. endchoice config GLOB @@ -402,7 +413,7 @@ config DEFAULT_ENVIRONMENT config DEFAULT_ENVIRONMENT_GENERIC bool depends on DEFAULT_ENVIRONMENT - select SHELL_HUSH + depends on SHELL_HUSH select HUSH_GETOPT select CMD_CRC select CMD_CRC_CMP -- 1.7.2.3 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
