nuttx

History

Xiang Xiao 0ff29e8f10 libc/stdlib: Compile lib_openpty.c without checking CONFIG_SERIAL_TERMIOS follow up the following change: commit `4262b09cbf` Author: Xiang Xiao <xiaoxiang@xiaomi.com> Date: Fri Dec 17 02:58:49 2021 +0800 libc: Implement terminal api regardless of CONFIG_SERIAL_TERMIOS setting since many functions aren't related to termios directly Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>		2022-02-03 22:51:28 +01:00
..
libc	libc/stdlib: Compile lib_openpty.c without checking CONFIG_SERIAL_TERMIOS	2022-02-03 22:51:28 +01:00
libdsp	Remove the unnecessary inclusion of assert.h and string.h from public header files	2021-12-20 10:30:08 +01:00
libnx	include: fix double include pre-processor guards	2022-01-16 11:11:14 -03:00
libxx	libxx:uclibxx: add patch use overload constructor of filebuf & ostream	2022-01-24 23:26:59 +08:00
README.txt	libs/README.txt: Fix a typo	2020-01-27 08:46:46 +01:00

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.