Remove make preinstall

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.

1 files changed, 91 insertions, 0 deletions

diff --git a/cpukit/include/rtems/score/corebarrier.h b/cpukit/include/rtems/score/corebarrier.h
new file mode 100644
index 0000000000..ba706be3e3
--- /dev/null
+++ b/cpukit/include/rtems/score/corebarrier.h
@@ -0,0 +1,91 @@
+/**
+ *  @file rtems/score/corebarrier.h
+ *
+ *  @brief Constants and Structures Associated with the Barrier Handler
+ *
+ *  This include file contains all the constants and structures associated
+ *  with the Barrier Handler.
+ */
+
+/*
+ *  COPYRIGHT (c) 1989-2007.
+ *  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.
+ */
+
+#ifndef _RTEMS_SCORE_COREBARRIER_H
+#define _RTEMS_SCORE_COREBARRIER_H
+
+#include <rtems/score/threadq.h>
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/**
+ *  @defgroup ScoreBarrier Barrier Handler
+ *
+ *  @ingroup Score
+ *
+ *  This handler encapsulates functionality which provides the foundation
+ *  Barrier services used in all of the APIs supported by RTEMS.
+ */
+/**@{*/
+
+/**
+ *  Flavors of barriers.
+ */
+typedef enum {
+  /** This specifies that the barrier will automatically release when
+   *  the user specified number of threads have arrived at the barrier.
+   */
+  CORE_BARRIER_AUTOMATIC_RELEASE,
+  /** This specifies that the user will have to manually release the barrier
+   *  in order to release the waiting threads.
+   */
+  CORE_BARRIER_MANUAL_RELEASE
+}   CORE_barrier_Disciplines;
+
+/**
+ *  The following defines the control block used to manage the
+ *  attributes of each barrier.
+ */
+typedef struct {
+  /** This field indicates whether the barrier is automatic or manual.
+   */
+  CORE_barrier_Disciplines  discipline;
+  /** This element indicates the number of threads which must arrive at the
+   *  barrier to trip the automatic release.
+   */
+  uint32_t                  maximum_count;
+}   CORE_barrier_Attributes;
+
+/**
+ *  The following defines the control block used to manage each
+ *  barrier.
+ */
+typedef struct {
+  /** This field is the Waiting Queue used to manage the set of tasks
+   *  which are blocked waiting for the barrier to be released.
+   */
+  Thread_queue_Control     Wait_queue;
+  /** This element is the set of attributes which define this instance's
+   *  behavior.
+   */
+  CORE_barrier_Attributes  Attributes;
+  /** This element contains the current number of thread waiting for this
+   *  barrier to be released. */
+  uint32_t                 number_of_waiting_threads;
+}   CORE_barrier_Control;
+
+/**@}*/
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif
+/*  end of include file */