source: rtems/cpukit/include/rtems/score/corebarrier.h @ 21275b58

Last change on this file since 21275b58 was 2afb22b, checked in by Chris Johns <chrisj@…>, on Dec 23, 2017 at 7:18:56 AM

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.

  • Property mode set to 100644
File size: 2.3 KB
Line 
1/**
2 *  @file rtems/score/corebarrier.h
3 *
4 *  @brief Constants and Structures Associated with the Barrier Handler
5 *
6 *  This include file contains all the constants and structures associated
7 *  with the Barrier Handler.
8 */
9
10/*
11 *  COPYRIGHT (c) 1989-2007.
12 *  On-Line Applications Research Corporation (OAR).
13 *
14 *  The license and distribution terms for this file may be
15 *  found in the file LICENSE in this distribution or at
16 *  http://www.rtems.org/license/LICENSE.
17 */
18
19#ifndef _RTEMS_SCORE_COREBARRIER_H
20#define _RTEMS_SCORE_COREBARRIER_H
21
22#include <rtems/score/threadq.h>
23
24#ifdef __cplusplus
25extern "C" {
26#endif
27
28/**
29 *  @defgroup ScoreBarrier Barrier Handler
30 *
31 *  @ingroup Score
32 *
33 *  This handler encapsulates functionality which provides the foundation
34 *  Barrier services used in all of the APIs supported by RTEMS.
35 */
36/**@{*/
37
38/**
39 *  Flavors of barriers.
40 */
41typedef enum {
42  /** This specifies that the barrier will automatically release when
43   *  the user specified number of threads have arrived at the barrier.
44   */
45  CORE_BARRIER_AUTOMATIC_RELEASE,
46  /** This specifies that the user will have to manually release the barrier
47   *  in order to release the waiting threads.
48   */
49  CORE_BARRIER_MANUAL_RELEASE
50}   CORE_barrier_Disciplines;
51
52/**
53 *  The following defines the control block used to manage the
54 *  attributes of each barrier.
55 */
56typedef struct {
57  /** This field indicates whether the barrier is automatic or manual.
58   */
59  CORE_barrier_Disciplines  discipline;
60  /** This element indicates the number of threads which must arrive at the
61   *  barrier to trip the automatic release.
62   */
63  uint32_t                  maximum_count;
64}   CORE_barrier_Attributes;
65
66/**
67 *  The following defines the control block used to manage each
68 *  barrier.
69 */
70typedef struct {
71  /** This field is the Waiting Queue used to manage the set of tasks
72   *  which are blocked waiting for the barrier to be released.
73   */
74  Thread_queue_Control     Wait_queue;
75  /** This element is the set of attributes which define this instance's
76   *  behavior.
77   */
78  CORE_barrier_Attributes  Attributes;
79  /** This element contains the current number of thread waiting for this
80   *  barrier to be released. */
81  uint32_t                 number_of_waiting_threads;
82}   CORE_barrier_Control;
83
84/**@}*/
85
86#ifdef __cplusplus
87}
88#endif
89
90#endif
91/*  end of include file */
Note: See TracBrowser for help on using the repository browser.