Bitbucket Issue 5, apps build system: The previous patch wasn't complete, it was just idea how to resolve issue.  Please, find attached issue5.patch to resolve it. It can be applied on top current apps/master. From Artur Mądrzak.

Issue 5:  I found an unexpected behavior in apps/ configuration generation. Adding external symbolic link in apps/ directory and using Make.defs for Kconfig generation, Kconfig file has a wrong path in the source argument. It contains original dir path outside of the source tree instead path to sub-directory in apps/.

The problem is connected with make/system symbolic link path resolution.  Corrected by a patch submitted by Artur Mądrzak with Issue 5.

Signed-off-by: Marco Krahl <ocram.lhark@gmail.com>

apps/examples/bridge:  Add a simple UDP relay bridge for testing configurations with multiple networks

BAS: Rename examples/bas to examples/bastest.  Hook into build and configuration system.  Finish ROMFS logic

Add an install target to all makefiles.  For the import build, the top-level Makefile now does two passes: (1) builds libapp.a, then (2) installs the programs (not yet finished)

Add support for a network device IOCTL to access PHY registers.  Ioctls only implemented for STM32.  From Lazlo

Mov apps/examples/composite to apps/system/composite; convert configs/stm3210e-eval/composite to use kconfig-frontend tools -- untested

Remove CONFIG_XYZ_BUILTIN configurations, replace with the single CONFIG_NSH_BUILTIN_APPS.  Add SAM3/4 sam_periphclks.h which is just a header file that includes the right header file.  Misc SAM3U-EK cleanup

Move SAM3U header files to arch/arm/src/sam3u/chip. Some renaming of SAM3U to SAM to ssupport SAM4.  Convert all configs/sam3u-ek configurations to use the kconfig-frontends tool

Add apps/examples/slcd, Remove USB from STM32L-Discovery, LSE support for the STM32 L family, some STM32L-Discovery LCD debug changes

apps/examples/helloxx entry point name was mangled when built as an NSH builtin; plus some README updates

Rearchitecting of some MTD, partition, SMART interfaces, and FLASH drivers to:  Better use the byte write capbility when available and to use smaller erase sectors for the erase sector size when available).

Add support for the byte write method to MTD partition logic;  Beef up the MTD partition test -- and fix resulting bugs detected