Gregory Nutt e3e911555a apps/system/system and popen: Adapt so that these can be used in the KERNEL build mode. In this case, simply replace task_spawn() with posix_spawn(). This depends on the existence of some environment where /bin/sh exists and can be used to execute one NSH command. For the case of system(), this change was more complete because it previously used task_create(). Now it uses either task_spawn() or posix_spawn(), depending upon the configuration.		2018-08-18 07:55:23 -06:00
..
.gitignore	apps/system/popen: Add an implementation of the standard popen() and pclose() OS interfaces. These are implementated as applications vs. part of the OS because they depend on NSH. Untested on initial commit.	2018-08-17 10:45:06 -06:00
Kconfig	apps/system/system and popen: Adapt so that these can be used in the KERNEL build mode. In this case, simply replace task_spawn() with posix_spawn(). This depends on the existence of some environment where /bin/sh exists and can be used to execute one NSH command. For the case of system(), this change was more complete because it previously used task_create(). Now it uses either task_spawn() or posix_spawn(), depending upon the configuration.	2018-08-18 07:55:23 -06:00
Make.defs	apps/system/popen: Add an implementation of the standard popen() and pclose() OS interfaces. These are implementated as applications vs. part of the OS because they depend on NSH. Untested on initial commit.	2018-08-17 10:45:06 -06:00
Makefile	apps/system/popen: Add an implementation of the standard popen() and pclose() OS interfaces. These are implementated as applications vs. part of the OS because they depend on NSH. Untested on initial commit.	2018-08-17 10:45:06 -06:00
popen.c	apps/system/system and popen: Adapt so that these can be used in the KERNEL build mode. In this case, simply replace task_spawn() with posix_spawn(). This depends on the existence of some environment where /bin/sh exists and can be used to execute one NSH command. For the case of system(), this change was more complete because it previously used task_create(). Now it uses either task_spawn() or posix_spawn(), depending upon the configuration.	2018-08-18 07:55:23 -06:00