| Commit message (Collapse) | Author | Files | Lines |
|
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 assert helps to detect an invalid reference counting in RTEMS_DEBUG
configurations.
Update #3132.
|
|
Update #3136.
|
|
Check iop reference count in close() and return -1 with errno set to
EBUSY in case the file descriptor is still in use.
Update #3132.
|
|
Update #3132.
|
|
Replace rtems_libio_check_fd(), rtems_libio_iop(),
rtems_libio_check_open() and rtems_libio_check_permissions()
combinations with new LIBIO_GET_IOP() and LIBIO_GET_IOP_WITH_ACCESS()
macros.
Update #3132.
|
|
Update #3132.
|
|
Update #3132.
|
|
Rename rtems_libio_check_permissions_with_error() in
rtems_libio_check_permissions().
Update #3132.
|
|
Remove rtems_libio_check_permissions() and convert single user to
rtems_libio_check_permissions_with_error().
Update #3132.
|
|
This simplifies error handling later.
Update #3132.
|
|
Remove the file descriptor validation. This is the job of
rtems_libio_check_fd(). Use an inline function instread of a macro.
Update #3132.
|
|
The top-level IO library structures should contain no special-case data.
Update #2859.
|
|
Update #2859.
|
|
Perform a context-dependent deferred location release to avoid a
deadlock on the file system instance locks, for example during a
chdir().
Update #2936.
|
|
Add path length parameter to
rtems_filesystem_eval_path_start_with_root_and_current() so that users
may pass paths without a '\0' termination.
Update #2558.
|
|
|
|
Drop parameter check from previously unused
rtems_libio_iop_to_descriptor().
|
|
|
|
|
|
Use the fstat handler instead.
|
|
|
|
|
|
|
|
|
|
Add a local context structure to the SMP lock API for acquire and
release pairs. This context can be used to store the ISR level and
profiling information. It may be later used to enable more
sophisticated lock algorithms, e.g. MCS locks.
There is only one lock that cannot be used with a local context. This
is the per-CPU lock since here we would have to transfer the local
context through a context switch which is very complicated.
|
|
|
|
|
|
Split the dub call into dup and dup2 in fcntl.c. This requires
a private command which is placed in the internal libio header.
|
|
Implement POSIX requirements in the high-level file system layer. Use
common implementation for all change owner variants.
|
|
Implement POSIX requirements in the high-level file system layer.
|
|
|
|
This is the result of a sed script which converts all uses
of @{ into a consistent form.
|
|
|
|
|
|
|
|
http://www.google-melange.com/gci/task/view/google/gci2012/7996208
|
|
|
|
|
|
|
|
|
|
http://www.google-melange.com/gci/task/view/google/gci2012/8009205
|
|
http://www.google-melange.com/gci/task/view/google/gci2012/7975223
|
|
http://www.google-melange.com/gci/task/view/google/gci2012/7992211
|
|
http://www.google-melange.com/gci/task/view/google/gci2012/8017203
|
|
|
|
http://www.google-melange.com/gci/task/view/google/gci2012/7992210
|
|
|
|
Rename rtems_filesystem_location_exists_in_same_fs_instance_as() into
rtems_filesystem_location_exists_in_same_instance_as() for consistency
with other file system instance related functions.
|