2012-09-17 15:18:44 -03:00
|
|
|
#
|
|
|
|
|
# For a description of the syntax of this configuration file,
|
|
|
|
|
# see misc/tools/kconfig-language.txt.
|
|
|
|
|
#
|
|
|
|
|
|
2012-12-23 16:22:41 -04:00
|
|
|
config BUILTIN
|
|
|
|
|
bool "Support Builtin Applications"
|
2012-09-17 15:18:44 -03:00
|
|
|
default n
|
|
|
|
|
---help---
|
2012-12-23 16:22:41 -04:00
|
|
|
Enable support for builtin applications. This features assigns a string
|
2012-09-17 15:18:44 -03:00
|
|
|
name to an application. This feature is also the underlying requirement
|
|
|
|
|
to support built-in applications in the NuttShell (NSH).
|
|
|
|
|
|
2012-12-23 16:22:41 -04:00
|
|
|
if BUILTIN
|
2013-01-14 15:22:32 -04:00
|
|
|
|
|
|
|
|
config APPS_BINDIR
|
|
|
|
|
bool "BINFS File System"
|
|
|
|
|
default n
|
|
|
|
|
---help---
|
|
|
|
|
The BINFS file system is current just a toy. The BINFS may, for example,
|
|
|
|
|
be mount at /bin. Then all of the built-in applications will appear as
|
|
|
|
|
executable file in /bin if you list them from NSH like:
|
|
|
|
|
|
|
|
|
|
nsh> ls -l /bin
|
|
|
|
|
|
|
|
|
|
At present, the BINFS supports nothing more than that. It is planned,
|
|
|
|
|
however, to support execution of the builtin applications from BINFS as
|
|
|
|
|
well (via a binfmt/ loader). However, that is down the road.
|
|
|
|
|
|
2012-09-17 15:18:44 -03:00
|
|
|
endif
|
