diff --git a/Documentation/NuttXBinfmt.html b/Documentation/NuttXBinfmt.html index b6c19e9cdc..653d1ea198 100644 --- a/Documentation/NuttXBinfmt.html +++ b/Documentation/NuttXBinfmt.html @@ -186,7 +186,7 @@ struct binary_s -

2.3.8 exepath_init()

+

2.3.8 envpath_init()

Function Prototype:

Description:

@@ -361,31 +361,31 @@ EXEPATH_HANDLE exepath_init(void);

  1. - Call exepath_init() to initialize for the traversal. - exepath_init() will return an opaque handle that can then be provided to exepath_next() and exepath_release(). + Call envpath_init() to initialize for the traversal. + envpath_init() will return an opaque handle that can then be provided to envpath_next() and envpath_release().
  2. - Call exepath_next() repeatedly to examine every file that lies in the directories of the PATH variable. + Call envpath_next() repeatedly to examine every file that lies in the directories of the PATH variable.
  3. - Call exepath_release() to free resources set aside by exepath_init(). + Call envpath_release() to free resources set aside by envpath_init().

Input Parameters: None

Returned Value:

-

2.3.9 exepath_next()

+

2.3.9 envpath_next()

Function Prototype:

Description:

@@ -394,7 +394,7 @@ FAR char *exepath_next(EXEPATH_HANDLE handle, FAR const char *relpath);

Input Parameters:

Returned Value:

@@ -410,27 +410,27 @@ FAR char *exepath_next(EXEPATH_HANDLE handle, FAR const char *relpath);

NULLrelpath from any absolute path in the PATH variable. - In this case, there is no point in calling exepath_next() further; exepath_release() must be called to release resources set aside by expath_init(). + In this case, there is no point in calling envpath_next() further; envpath_release() must be called to release resources set aside by expath_init().

-

2.3.10- exepath_release()

+

2.3.10- envpath_release()

Function Prototype:

Description:

Input Parameters:

Returned Value: None

diff --git a/Documentation/NuttxUserGuide.html b/Documentation/NuttxUserGuide.html index b2328be4fa..fea8cf2840 100644 --- a/Documentation/NuttxUserGuide.html +++ b/Documentation/NuttxUserGuide.html @@ -875,7 +875,7 @@ int exec(FAR const char *filename, FAR char * const *argv,
  • filename: The path to the program to be executed. - If CONFIG_BINFMT_EXEPATH is defined in the configuration, then this may be a relative path from the current working directory. + If CONFIG_LIB_ENVPATH is defined in the configuration, then this may be a relative path from the current working directory. Otherwise, path must be the absolute path to the program.
  • @@ -969,7 +969,7 @@ int execv(FAR const char *path, FAR char *const argv[]);
  • path: The path to the program to be executed. - If CONFIG_BINFMT_EXEPATH is defined in the configuration, then this may be a relative path from the current working directory. + If CONFIG_LIB_ENVPATH is defined in the configuration, then this may be a relative path from the current working directory. Otherwise, path must be the absolute path to the program.
  • @@ -1013,7 +1013,7 @@ int execl(FAR const char *path, ...);
  • path: The path to the program to be executed. - If CONFIG_BINFMT_EXEPATH is defined in the configuration, then this may be a relative path from the current working directory. + If CONFIG_LIB_ENVPATH is defined in the configuration, then this may be a relative path from the current working directory. Otherwise, path must be the absolute path to the program.
  • @@ -1074,7 +1074,7 @@ int posix_spawnp(FAR pid_t *pid, FAR const char *file,

    NOTE: NuttX provides only one implementation: - If CONFIG_BINFMT_EXEPATH is defined, then only posix_spawnp() behavior is supported; otherwise, only posix_spawn behavior is supported. + If CONFIG_LIB_ENVPATH is defined, then only posix_spawnp() behavior is supported; otherwise, only posix_spawn behavior is supported.

  • @@ -1156,8 +1156,8 @@ int posix_spawnp(FAR pid_t *pid, FAR const char *file,