forked from Imagelibrary/rtems
2afb22b7e1
A speciality of the RTEMS build system was the make preinstall step. It copied header files from arbitrary locations into the build tree. The header files were included via the -Bsome/build/tree/path GCC command line option. This has at least seven problems: * The make preinstall step itself needs time and disk space. * Errors in header files show up in the build tree copy. This makes it hard for editors to open the right file to fix the error. * There is no clear relationship between source and build tree header files. This makes an audit of the build process difficult. * The visibility of all header files in the build tree makes it difficult to enforce API barriers. For example it is discouraged to use BSP-specifics in the cpukit. * An introduction of a new build system is difficult. * Include paths specified by the -B option are system headers. This may suppress warnings. * The parallel build had sporadic failures on some hosts. This patch removes the make preinstall step. All installed header files are moved to dedicated include directories in the source tree. Let @RTEMS_CPU@ be the target architecture, e.g. arm, powerpc, sparc, etc. Let @RTEMS_BSP_FAMILIY@ be a BSP family base directory, e.g. erc32, imx, qoriq, etc. The new cpukit include directories are: * cpukit/include * cpukit/score/cpu/@RTEMS_CPU@/include * cpukit/libnetworking The new BSP include directories are: * bsps/include * bsps/@RTEMS_CPU@/include * bsps/@RTEMS_CPU@/@RTEMS_BSP_FAMILIY@/include There are build tree include directories for generated files. The include directory order favours the most general header file, e.g. it is not possible to override general header files via the include path order. The "bootstrap -p" option was removed. The new "bootstrap -H" option should be used to regenerate the "headers.am" files. Update #3254.
#
# COPYRIGHT (c) 1989-1999.
# On-Line Applications Research Corporation (OAR).
#
# The license and distribution terms for this file may be
# found in the file LICENSE in this distribution or at
# http://www.rtems.org/license/LICENSE.
This directory contains the RTEMS Sample Application Suite.
The tests in this directory perform two functions:
+ provide simple examples of applications which can be
used as a starting point for your application.
+ help test a new board support package
The hello and ticker applications are useful when first bringing up
a new board support package. The base_mp test is useful when
performing initial checkout on a new MPCI layer.
The following describes each of the sample applications:
base_mp
This is a very simple two node multiprocessor application. It consists
of a single initialization task on each node which print out
their respective node numbers and task IDs. This test can be
used as a simple test of a new MPCI layer because it minimizes
the number of packets sent by RTEMS.
This is intended as a starting point for custom developed multiprocessor
applications.
base_sp
This is a simple single processor application which consists of
an initialization task which creates another task.
This is intended as a starting point for custom developed single
processor applications.
capture
This simple application starts the monitor and allows you access
to the capture engine. The capture engine provides a trace of
RTEMS activity and is used to debug your application.
cdtest
A very simple C++ application which demonstrates that it is
possible to use C++ contructors and destructors in an RTEMS
application. Also does a perfunctory iostream test.
hello
This is the RTEMS version of the classic hello world program.
It consists of single initialization task which prints out
a few messages.
This test does not include a Clock Tick device driver and can
be used to test the startup code of the board support package
as well as console output.
paranoia
A public domain test of the floating point and math library
capabilities of a toolset. It reports discrepancies between
actual and expected results. It is a large test.
ticker
This is a simple test of the user's Clock Tick device driver.
This test has an initialization task create three application
tasks which sleep and periodically wake up and print the time.
unlimited
This is a test for the umlimited object feature of RTEMS. Here
you can configure RTEMS to give as many objects as memory
in the Workspace.