include/nuttx/nxmu.h: Due the name change, the nxmu_start() belongs more appropriately in nxmu.h than nx.h.

This commit is contained in:
Gregory Nutt 2019-02-04 17:48:30 -06:00
parent 7a2bb1f727
commit 193e9af6f6
4 changed files with 27 additions and 26 deletions

View File

@ -48,7 +48,7 @@
#include <nuttx/board.h>
#include <nuttx/lib/modlib.h>
#include <nuttx/binfmt/symtab.h>
#include <nuttx/nx/nx.h>
#include <nuttx/nx/nxmu.h>
#ifdef CONFIG_BOARDCTL_USBDEVCTRL
# include <nuttx/usb/cdcacm.h>

View File

@ -50,6 +50,7 @@
#include <nuttx/signal.h>
#include <nuttx/kthread.h>
#include <nuttx/nx/nx.h>
#include <nuttx/nx/nxmu.h>
#include "nxfe.h"

View File

@ -269,31 +269,6 @@ extern "C"
int nx_runinstance(FAR const char *mqname, FAR NX_DRIVERTYPE *dev);
#define nx_run(dev) nx_runinstance(NX_DEFAULT_SERVER_MQNAME, dev)
/****************************************************************************
* Name: nxmu_start
*
* Description:
* nxmu_start() provides a wrapper function to simplify and standardize
* the starting of the NX server.
*
* nxmu_start() can be called (indirectly) from applications via the
* boardctl() interface with the BOARDIOC_NX_START command.
*
* Input Parameters:
* None
*
* Returned Value:
* Zero (OK) is returned on success. This indicates that the NX server
* has been successfully started, is running, and waiting to accept
* connections from NX clients.
*
* A negated errno value is returned on failure. The errno value indicates
* the nature of the failure.
*
****************************************************************************/
int nxmu_start(void);
/****************************************************************************
* Name: nx_connectinstance (and nx_connect macro)
*

View File

@ -473,6 +473,31 @@ extern "C"
* Public Functions
****************************************************************************/
/****************************************************************************
* Name: nxmu_start
*
* Description:
* nxmu_start() provides a wrapper function to simplify and standardize
* the starting of the NX server.
*
* nxmu_start() can be called (indirectly) from applications via the
* boardctl() interface with the BOARDIOC_NX_START command.
*
* Input Parameters:
* None
*
* Returned Value:
* Zero (OK) is returned on success. This indicates that the NX server
* has been successfully started, is running, and waiting to accept
* connections from NX clients.
*
* A negated errno value is returned on failure. The errno value indicates
* the nature of the failure.
*
****************************************************************************/
int nxmu_start(void);
/****************************************************************************
* Name: nxfe_constructwindow
*