nuttx

History

Xiang Xiao 9928088868 libc: Don't fclose and fopen file in freopen to avoid FILE pointer change after this commit: commit `b0797263ca` Author: Xiang Xiao <xiaoxiang@xiaomi.com> Date: Thu Aug 13 18:17:29 2020 +0800 libc/stdio: Allocate file_struct dynamically 1.Reduce the default size of task_group_s(~512B each task) 2.Scale better between simple and complex application Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>		2020-10-19 21:31:31 -07:00
..
libc	libc: Don't fclose and fopen file in freopen	2020-10-19 21:31:31 -07:00
libdsp	Fix nxstyle warnings	2020-10-10 12:24:28 -06:00
libnx	use "export" to expose TOPDIR to all child make instead of passing it around every time	2020-09-15 21:11:33 -07:00
libxx	libxx: Switch the package downloading from 11.0.0.rc1 to 11.0.0	2020-10-12 20:33:55 +01: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.