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.
This directory contains the RTEMS POSIX Timing Test Suite. The tests in this directory are used to measure the execution time of RTEMS directive and some critical internal functions. The results of these test are useful for comparison of RTEMS performance + between versions of RTEMS + between different boards + across different architectures These tests attempt to benchmark RTEMS as the user would. They measure the execution time for a directive (under various circumstances) from the time RTEMS is entered until it is executed. Where possible, the time is the average of at least 100 invocations of the directive. The accuracy of the times reported by these benchmarks is very dependent on the resolution of the timer being used. It is also important to insure that all sources of hardware interrupts are disabled during execution of the tests. This insures that the directive time reported does not include any interrupt time. The file psxtmtests_plan.csv contains the development plan for this test suite. It is a PLAN which indicates which tests are to contain which test cases, the test name, and which template in rtems-testing/rtems-test-templates are to be used for their construction. This is just a plan. There may need to be more test cases for a particular service to effectively measure all interesting non-error use cases.