2012-04-06 18:33:17 +02:00
|
|
|
#
|
|
|
|
# For a description of the syntax of this configuration file,
|
2012-04-06 18:45:52 +02:00
|
|
|
# see misc/tools/kconfig-language.txt.
|
2012-04-06 18:33:17 +02:00
|
|
|
#
|
2012-04-14 22:01:08 +02:00
|
|
|
|
2012-12-23 21:22:41 +01:00
|
|
|
config BUILTIN
|
|
|
|
bool "Support Builtin Applications"
|
2012-04-14 22:01:08 +02:00
|
|
|
default n
|
|
|
|
---help---
|
2012-12-23 21:22:41 +01:00
|
|
|
Enable support for builtin applications. This features assigns a string
|
2012-04-14 22:01:08 +02:00
|
|
|
name to an application. This feature is also the underlying requirement
|
|
|
|
to support built-in applications in the NuttShell (NSH).
|
|
|
|
|
2012-12-23 21:22:41 +01:00
|
|
|
if BUILTIN
|
2013-01-14 20:22:32 +01: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.
|
|
|
|
|
2013-01-15 22:01:37 +01:00
|
|
|
config BUILTIN_PROXY_STACKSIZE
|
|
|
|
int "Builtin Proxy Stack Size"
|
|
|
|
default 1024
|
|
|
|
---help---
|
|
|
|
If exec_builting uses I/O redirection options, then it will require
|
|
|
|
an intermediary/proxy task to muck with the file descriptors. This
|
|
|
|
configuration item specifies the stack size used for the proxy. Default:
|
|
|
|
1024 bytes.
|
|
|
|
|
2012-04-14 22:01:08 +02:00
|
|
|
endif
|