zephyr/lib/CMakeLists.txt

add_subdirectory(crc)
add_subdirectory_ifdef(CONFIG_JSON_LIBRARY          json)
if(NOT CONFIG_NATIVE_APPLICATION)
add_subdirectory(libc)
endif()
add_subdirectory_if_kconfig(ring_buffer)
add_subdirectory_if_kconfig(base64)
add_subdirectory(mempool)
add_subdirectory_ifdef(CONFIG_PTHREAD_IPC          posix)
lib: move crc from drivers to lib/ Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-15 02:44:49 +08:00			`add_subdirectory(crc)`
libc: some architectures do not require baremetal libc When building a native application, we use the host provided libc, so do not build minimal libc or newlib. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-22 08:26:00 +08:00			`add_subdirectory_ifdef(CONFIG_JSON_LIBRARY json)`
			`if(NOT CONFIG_NATIVE_APPLICATION)`
lib: move crc from drivers to lib/ Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-15 02:44:49 +08:00			`add_subdirectory(libc)`
libc: some architectures do not require baremetal libc When building a native application, we use the host provided libc, so do not build minimal libc or newlib. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-22 08:26:00 +08:00			`endif()`
lib: move ring_buffer from misc/ to lib/ Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-15 02:57:03 +08:00			`add_subdirectory_if_kconfig(ring_buffer)`
lib: Add base64 library Since base64 is such a simple and commonly used feature it makes no sense to build the whole of mbedTLS for it. Instead take the implementation that comes with mbedTLS and import it as a native library outside of ext/ for all to use directly. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> 2018-03-23 03:05:26 +08:00			`add_subdirectory_if_kconfig(base64)`
lib: user mode compatible mempools We would like to offer the capability to have memory pool heap data structures that are usable from user mode threads. The current k_mem_pool implementation uses IRQ locking and system-wide membership lists that make it incompatible with user mode constraints. However, much of the existing memory pool code can be abstracted to some common functions that are used by both k_mem_pool and the new sys_mem_pool implementations. The sys_mem_pool implementation has the following differences: * The alloc/free APIs work directly with pointers, no internal memory block structures are exposed to the end user. A pointer to the source pool is provided for allocation, but freeing memory just requires the pointer and nothing else. * k_mem_pool uses IRQ locks and required very fine-grained locking in order to not affect system latency. sys_mem_pools just use a semaphore to protect the pool data structures at the API level, since there aren't implications for system responsiveness with this kind of concurrency control. * sys_mem_pools do not support the notion of timeouts for requesting memory. * sys_mem_pools are specified at compile time with macros, just like kernel memory pools. Alternative forms of specification at runtime will be a later enhancement. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2018-03-07 09:12:37 +08:00			`add_subdirectory(mempool)`
lib: posix: Move posix layer from 'kernel' to 'lib' Move posix layer from 'kernel' to 'lib' folder as it is not a core kernel feature. Fixed posix header file dependencies as part of the move and also removed NEWLIBC related macros from posix headers. Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com> 2018-04-06 01:11:15 +08:00			`add_subdirectory_ifdef(CONFIG_PTHREAD_IPC posix)`