The following makefiles use Application.mk but did not define APPNAME, which
probably does Bad Things since APPNAME is used for app registration, for example:
I added the definitions to these files. Do you want a patch?
I also developed a way to automatically create a link from apps/include/APPNAME
to SUBDIR/APPNAME/export. This is very useful for libraries that publish headers
usable by other apps.
Now an app is not split in two places anymore, everything related to "libacme"
is in examples/libacme/*, instead of BOTH examples/libacme/* and
include/libacme. This is also very useful for custom apps/libraries.
The link is set up during the depend target if the application folder contains a
dir called "export", and teared down during distclean.
It only uses make syntax and the provided (un)link[.sh|.bat] tools.
NOTE: I will probably soon provide an alternative to Kmenu files, a MENU=thing
in Makefiles that use Directory.mk seems FAR more practical. I should have done
Post by Sebastien Lorquet ***@lorquet.fr [nuttx]
I see that some apps, that uses Application,mk, uses APPNAME as the application
name, but the variable PROGNAME is also used.
What is the difference between the two?
For example, in sched_note I understand that APPNAME is the name of the app but
PROGNAME is the name of the generated binary file for app builds.
On the contrary examples/wget only defines PROGNAME but no APPNAME
Is that an error? How to deal with it? Change every makefile that references
Application.mk, or, in the same file, define APPNAME=PROGNAME if APPNAME is not
- all makefiles shall define APPNAME
- Application.mk computes PROGNAME if it is not already defined in individual
What do you think?