incubator-nuttx

History

Ville Juven 172b209f2d sched/assert: Re-implement assert() into user space _assert is a kernel procedure, entered via system call to make the core dump in privileged mode. Running exit() from this context is not OK as it runs the registered exit functions and flushes streams, which must not be done from privileged mode as it is a security hole. Thus, implement assert() into user space (again) and remove the exit() call from the kernel procedure.		2022-12-22 21:07:47 +08:00
..
libc	sched/assert: Re-implement assert() into user space	2022-12-22 21:07:47 +08:00
libdsp	nuttx: unify MIN, MAX and ABS macro definition across the code	2022-12-21 09:31:28 +08:00
libnx	tools: replace INCDIR to Makefile variable	2022-11-03 19:59:55 +08:00
libxx	Don't download tarballs if a local git repo found	2022-12-05 10:47:36 +01:00
README.txt	…

README.txt

README
======

This directory holds NuttX libraries.  Libraries in NuttX are very special
creatures.  They have these properties:

1. They can be shared by both application logic and logic within the OS when
   using the FLAT build.

2. But in PROTECTED and KERNEL modes, they must be built differently:  The
   copies used by applications and the OS cannot be the same.  Rather,
   separate versions of libraries must be built for the kernel and for
   applications.

3. When used by the OS, some special care must be taken to assure that the
   OS logic does not disrupt the user's errno value and that the OS does
   not create inappropriate cancellation points.

   For example, sem_wait() is both a cancellation point and modifies the
   errno value.  So within the FLAT build and without kernel version for
   the PROTECTED and KERNEL builds, the special internal OS interface
   nxsem_wait() must be used.  Within libraries, the macro _SEM_WAIT()
   (as defined in include/nuttx/semaphore.h) is used instead.  The
   definition of this macro accounts for the different usage environments.

NOTE:  The libraries under libs/ build differently from other NuttX
components:  There are no build-related files in the libs/ directory; it
is simply a container for other well-known, individual library directories.
The upper level Makefile logic is aware of the libraries within the libs/
container.

The only real function of the libs/ directory is to prevent the top-level
directory from becoming cluttered with individual libraries.