Files
rtems/cpukit/libmisc/uuid
Chris Johns 2afb22b7e1 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.
2018-01-25 08:45:26 +01:00
..
2013-11-29 17:24:41 -06:00
2017-12-13 09:04:27 +01:00

uuid - DCE compatible Universally Unique Identifier library

The UUID library is used to generate unique identifiers for objects that may be
accessible beyond the local system.  This library generates UUIDs compatible
with those created by the Open Software Foundation (OSF) Distributed Computing
Environment (DCE) utility uuidgen.

The UUIDs generated by this library can be reasonably expected to be unique
within a system, and unique across all systems.  They could be used, for
instance, to generate unique HTTP cookies across multiple web servers without
communication between the servers, and without fear of a name clash.

This code is from the E2fsprogs project: http://e2fsprogs.sourceforge.net.
The package was e2fsprogs-libs-1.41.5.tar.gz.