Fork 0
patacongo 6a5794bec1 Need to clean NXFFS directory
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@3616 7fd9a85b-ad96-42d3-883c-3090e2eb8679
2011-05-15 23:26:10 +00:00
examples Need to clean NXFFS directory 2011-05-15 23:26:10 +00:00
include Move nuttx/include/apps to apps/include 2011-05-09 22:21:10 +00:00
interpreters More PIC32 header files 2011-05-11 17:21:47 +00:00
namedapp Add STM32 FLASH driver 2011-05-07 16:59:20 +00:00
netutils tools/mkdep.sh should not report an error if there are no files on the command line 2011-05-11 01:27:04 +00:00
nshlib Mostly cosmetic changes from Uros 2011-05-07 19:22:15 +00:00
system install updates from Uros 2011-05-12 18:10:00 +00:00
vsn install updates from Uros 2011-05-12 18:10:00 +00:00
ChangeLog.txt Prep for 6.3 release 2011-05-15 23:13:04 +00:00
Make.defs Renamed nuttapp to namedapp; add binfs to nammedapp/ 2011-03-28 13:01:57 +00:00
Makefile Incorporate install app from Uros 2011-05-12 14:49:46 +00:00
README.txt Remove .built_always 2011-04-01 14:30:43 +00:00


Application Folder

This folder provides various applications found in sub-directories.

Application entry points with their requirements are gathered together in 
in two files:

	- namedapp/namedapp_proto.h	Entry points, prototype function
	- namedapp/namedapp_list.h	Application specific information and requirements

The build occurs in several phases as different build targets are executed:
(1) contex, (2) depend, and (3) default (all). Application information is
collected during the make context build phase.

To execute an application function:

	exec_namedapp() is defined in the nuttx/include/apps/apps.h 
NuttShell provides transparent method of invoking the command, when the
following option is enabled:


in the NuttX configuration.

A special configuration file is used to configure which applications
are to be included in the build.  This file is configs/<board>/<configuration>/appconfig.
The existence of the appconfig file in the board configuration directory
is sufficient to enable building of applications.

The appconfig file is copied into the apps/ directory as .config when
NuttX is configured.  .config is included in the toplevel apps/Makefile.
As a minimum, this configuration file must define files to add to the

  CONFIGURED_APPS  += hello poweroff jvm

The form of each entry is <dir>=<dependency> when:

  <dir> is the name of a subdirectory in the apps directory, and

  <dependency> is a make dependency.  This will be "touch"-ed each time
  that the sub-directory is rebuilt.

When the user defines an option:
	CONFIG_BUILTIN_APP_START=<application name>
that application shall be invoked immediately after system starts.
Note that application name must be provided in ".." as: "hello", 
will call:
	int hello_main(int argc, char *argv[])

Application skeleton can be found under the hello sub-directory,
which shows how an application can be added to the project. One must

 1. create sub-directory as: appname
 2. provide entry point: appname_main()
 3. set the requirements in the file: Makefile, specially the lines:
	APPNAME		= appname
	ASRCS		= asm source file list as a.asm b.asm ...
	CSRCS		= C source file list as foo1.c foo2.c ..

 4. add application in the apps/Makefile