esp-idf/components/vfs/CMakeLists.txt

set(COMPONENT_SRCS "vfs.c"
                   "vfs_uart.c"
                   "vfs_semihost.c")
set(COMPONENT_ADD_INCLUDEDIRS "include")
register_component()

# Some newlib syscalls are implemented in vfs.c, make sure these are always
# seen by the linker
target_link_libraries(${COMPONENT_LIB} INTERFACE "-u vfs_include_syscalls_impl")
cmake: make main a component again 2018-09-10 21:44:12 -04:00			`set(COMPONENT_SRCS "vfs.c"`
vfs: Adds semihosting VFS driver 2019-02-19 14:50:18 -05:00			`"vfs_uart.c"`
			`"vfs_semihost.c")`
cmake: Remove defaults for COMPONENT_SRCDIRS, COMPONENT_SRCS, COMPONENT_ADD_INCLUDEDIRS * Philosophical: "explicit is better than implicit". * Practical: Allows useful errors if invalid directories given in components as the defaults aren't always used. Also trims the -I path from a number of components that have no actual include directory. * Simplifies knowing which components will be header-only and which won't 2018-01-19 00:22:08 -05:00			`set(COMPONENT_ADD_INCLUDEDIRS "include")`
build system: Initial cmake support, work in progress 2018-01-11 21:49:13 -05:00			`register_component()`
cmake: For gcc8 use linker to find paths to libc, libm, libstdc++, etc Removes the need to know/guess the paths to these libraries. Once we are gcc 8 only, we can remove -nostdlib and no additional arguments are needed for system libraries. The catch is: any time IDF overrides a symbol in the toolchain sysroot, we need an undefined linker marker to make sure this symbol is seen by linker. 2019-04-14 23:45:08 -04:00
			`# Some newlib syscalls are implemented in vfs.c, make sure these are always`
			`# seen by the linker`
cmake: use new signature form of target_link_library to link components !4452 used setting LINK_LIBRARIES and INTERFACE_LINK_LIBRARIES to link components built under ESP-IDF build system. However, LINK_LIBRARIES does not produce behavior same as linking PRIVATE. This MR uses the new signature for target_link_libraries directly instead. This also moves setting dependencies during component registration rather than after all components have been processed. The consequence is that internally, components have to use the new signature form as well. This does not affect linking the components to external targets, such as with idf_as_lib example. This only affects linking additional libraries to ESP-IDF libraries outside component processing (after idf_build_process), which is not even possible for CMake<v3.13 as target_link_libraries is not valid for targets not created in current directory. See https://cmake.org/cmake/help/v3.13/policy/CMP0079.html#policy:CMP0079 2019-06-04 07:05:33 -04:00			`target_link_libraries(${COMPONENT_LIB} INTERFACE "-u vfs_include_syscalls_impl")`