sergiotarxz/nuttx-apps
sergiotarxz/nuttx-apps
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update README file

Browse Source
This commit is contained in:
Gregory Nutt 2015-08-12 07:43:08 -06:00
parent 74801cf38e
commit 3a55ecabf8
2 changed files with 43 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ChangeLog.txt
View File

@ -1378,7 +1378,7 @@
directories. This means that to install a new application, you directories. This means that to install a new application, you
simply have to copy the directory (or link it) into the apps/ simply have to copy the directory (or link it) into the apps/
directory. If the new directory includes a Makefile and Make.defs directory. If the new directory includes a Makefile and Make.defs
file, the it will automatically be included in the build (2015-08-11). file, then it will automatically be included in the build (2015-08-11).
* apps/Makefile, Kconfig, */Kconfig, tools/mkkconfig.sh: Add the tool * apps/Makefile, Kconfig, */Kconfig, tools/mkkconfig.sh: Add the tool
mkkconfig.sh that dynamically builds the apps/Kconfig file at mkkconfig.sh that dynamically builds the apps/Kconfig file at
configuration time. The hardcoded configuration file has been removed configuration time. The hardcoded configuration file has been removed

71
README.txt
View File

@ -150,7 +150,7 @@ Building NuttX with Board-Specific Pieces Outside the Source Tree
Q: Has anyone come up with a tidy way to build NuttX with board- Q: Has anyone come up with a tidy way to build NuttX with board-
specific pieces outside the source tree? specific pieces outside the source tree?
A: Here are four: A: Here are three:
1) There is a make target called 'make export'. It will build 1) There is a make target called 'make export'. It will build
NuttX, then bundle all of the header files, libaries, startup NuttX, then bundle all of the header files, libaries, startup
@ -176,38 +176,51 @@ A: Here are four:
3) If you like the random collection of stuff in the apps/ directory 3) If you like the random collection of stuff in the apps/ directory
but just want to expand the existing components with your own, but just want to expand the existing components with your own,
external sub-directory then there is an easy way to that too: external sub-directory then there is an easy way to that too:
You just create the sympolic link at apps/external that You just create a sympolic link in the apps/ directory that
redirects to your application sub-directory. The apps/Makefile redirects to your application sub-directory.
will always automatically check for the existence of an
apps/external directory and if it exists, it will automatically
incorporate it into the build.
This feature of the apps/Makefile is documented only here. In order to be incorporated into the build, the directory that
you link under the apps/ directory should contain (1) a Makefile
that supports the clean and distclean targets (see other Makefiles
for examples), and (2) a tiny Make.defs file that simply adds the
custon build directories to the variable CONFIGURED_APPS like:
You can, for example, create a script called install.sh that CONFIGURED_APPS += my_directory1 my_directory2
The apps/Makefile will always automatically check for the
existence of subdirectories containing a Makefile and a Make.defs
file. The Makefile will be used only to support cleaning operations.
The Make.defs file provides the set of directories to be built; these
directories must also contain a Makefile. That Makefile must be able
to build the sources and add the objects to the apps/libapps.a archive.
(see other Makefiles for examples). It should support the all,
install, context, and depend targets.
apps/Makefile does not depend on any hardcoded lists of directories.
Instead, it does a wildcard search to find all appropriate
directories. This means that to install a new application, you
simply have to copy the directory (or link it) into the apps/
directory. If the new directory includes a Makefile and Make.defs
file, then it will automatically be included in the build.
If the directory that you add also includes a Kconfig file, then it
will automatically be included in the NuttX configuration system as
well. apps/Makefile uses a tool at apps/tools/mkkconfig.sh that
dynamically builds the apps/Kconfig file at pre-configuration time.
NOTE: The native Windows build is temporarily broken until a new
apps/tools/mkconfig.bat script is generated (2015-08-11).
You could, for example, create a script called install.sh that
installs a custom application, configuration, and board specific installs a custom application, configuration, and board specific
directory: directory:
a) Copy 'MyBoard' directory to configs/MyBoard. a) Copy 'MyBoard' directory to configs/MyBoard.
b) Add a symbolic link to MyApplication at apps/external b) Add a symbolic link to MyApplication at apps/external
c) Configure NuttX (usually by: c) Configure NuttX (usually by:
tools/configure.sh MyBoard/MyConfiguration tools/configure.sh MyBoard/MyConfiguration
or simply by copying defconfig->nuttx/.config, Use of the name ''apps/external'' is suggested because that name
setenv.sh->nuttx/setenv.sh, and Make.defs->nuttx/Make.defs. is included in the .gitignore file and will save you some nuisance
when working with GIT.
Using the 'external' link makes it especially easy to add a
'built-in' application an existing configuration.
4) Add any link to apps/
a) Add symbolic links apps/ to as many other directories as you
want,
b) Add the symbolic link to the list of candidate paths in the
top level apps/Makefile, and
b) Add the (relative) paths to the CONFIGURED_APPS list
in the Make.defs file in your new directory.
That is basically the same as my option #3 but doesn't use the
magic 'external' link.