0a107ca6d9
This commit adds support for custom stream via fopencookie function. The function allows the programmer the create his own custom stream for IO operations and hook his custom functions to it. This is a non POSIX interface defined in Standard C library and implemented according to it. The only difference is in usage of off_t instead of off64_t. Programmer can use 64 bits offset if CONFIG_FS_LARGEFILE is enabled. In that case off_t is defined as int64_t (int32_t otherwise). Field fs_fd is removed from file_struct and fs_cookie is used instead as a shared variable for file descriptor or user defined cookie. The interface will be useful for future fmemopen implementation. Signed-off-by: Michal Lenc <michallenc@seznam.cz> |
||
---|---|---|
.. | ||
libc | ||
libdsp | ||
libm | ||
libnx | ||
libxx | ||
CMakeLists.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.