| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Mention the type of the pointer in the parameter description. Use the
more general term "object" instead of "variable".
Update #3993.
|
| |
|
|
|
|
| |
Unify the wording across similar directives of other managers.
Update #3993.
|
| |
|
|
|
|
|
|
|
| |
Add a "Constraints" paragraph to the documentation.
Provide prototypes for programming language bindings. Use the macro
implementation to implement the corresponding functions.
Update #3993.
|
| |
|
|
|
|
|
| |
Place the paragraphs in the same order as the directive documentation in
the RTEMS Classic API Guide.
Update #3993.
|
| | |
|
| |
|
|
|
|
|
|
| |
Change license to BSD-2-Clause according to file histories and
documentation re-licensing agreement.
Update #3899.
Update #3993.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This directive has no implementation. It is documented in the RTEMS
Classic API Guide.
It was added by
commit 6c06288f6452da96fa630f1482aeaaba5d217531
Author: Joel Sherrill <joel.sherrill@OARcorp.com>
Date: Tue Jan 29 21:52:21 2008 +0000
without an implementation. The later change
commit fdc57ca4b6794dc17c7b7d94ae557da21e314d6a
Author: Joel Sherrill <joel.sherrill@OARcorp.com>
Date: Mon Nov 23 14:53:04 2009 +0000
renamed the similar rtems_object_id_api_minimum_class() in
rtems_object_api_minimum_class().
The rtems_object_api_maximum_class() is documented and implemented. It
can be assumed that the rtems_object_id_api_maximum_class() is a
fragement left over from development.
|
| |
|
|
|
|
| |
Move object related declarations and definitions to
<rtems/rtems/object.h>. The goal is to make <rtems.h> an include only
header file.
|
| |
|
|
| |
Update #3841.
|
| |
|
|
| |
Update #3706.
|
| |
|
|
| |
Update #3706.
|
| |
|
|
|
|
| |
This makes the @file documentation independent of the actual file name.
Update #3707.
|
|
|
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.
|
