blackbeard420/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf synced 2025-03-24 08:29:11 -04:00
Code Issues Projects Releases Wiki Activity
esp-idf/components/cxx/CMakeLists.txt

14 lines
464 B
CMake
Raw Normal View History

components: use new component registration api
2019-04-28 15:38:23 +08:00
idf_component_register(SRCS "cxx_exception_stubs.cpp"
"cxx_guards.cpp")
build system: Initial cmake support, work in progress
2018-01-12 13:49:13 +11:00
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 19:05:33 +08:00
target_link_libraries(${COMPONENT_LIB} PUBLIC stdc++ gcc)
target_link_libraries(${COMPONENT_LIB} INTERFACE "-u __cxa_guard_dummy")
build system: Initial cmake support, work in progress
2018-01-12 13:49:13 +11:00
Rename Kconfig options (root)
2019-04-24 15:02:25 +02:00
if(NOT CONFIG_COMPILER_CXX_EXCEPTIONS)
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 19:05:33 +08:00
target_link_libraries(${COMPONENT_LIB} INTERFACE "-u __cxx_fatal_exception")
build system: Initial cmake support, work in progress
2018-01-12 13:49:13 +11:00
endif()
C++: prepare RTTI support Ref. https://github.com/espressif/esp-idf/issues/1684 Also, for full RTTI support, libstdc++.a in the toolchain should be built in both with RTTI and w/o RTTI options. Multilib with -fno-rtti flag is used for that. Note that this commit does not actually enable RTTI support. The respective Kconfig option is hidden, and will be made visible when the toolchain is updated.
2019-10-31 10:15:54 +07:00
if(NOT CONFIG_COMPILER_CXX_RTTI)
target_link_libraries(${COMPONENT_LIB} PUBLIC -fno-rtti)
endif()
Reference in New Issue Copy Permalink