b94ce67899
This commit updates the get Zephyr settings functions to be able to handle settings if those settings are expressed using a generator expression. As example, zephyr_get_include_directories_for_lang(...) would prefix each include property of zephyr_interface with `-I`, like this: Property: include;include/generated;lib/libc/minimal/include becomes: `-Iinclude -Iinclude/generated -Ilib/libc/minimal/include` But if the property contains a generator expression: Property: include;$<TARGET_PROPERTY:compiler,some_include> becomes: -Iinclude -I$<TARGET_PROPERTY:compiler,some_include> and in case that property is a list, this results in: `-Iinclude -Iinclude/list_item1;include/list_item2;include/list_itemN` and thus breaking the build. This is fixed by using `$<JOIN:<list>>` expression instead, which ensures all list item, regardless of provided as simple list or through the usage another generator expression, will always expand correctly. Functions updated in the commit: - zephyr_get_include_directories_for_lang - zephyr_get_system_include_directories_for_lang - zephyr_get_compile_definitions_for_lang - zephyr_get_compile_options_for_lang The sample `application_development/external_lib` has been updated according to those changes. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> |
||
---|---|---|
.. | ||
clang | ||
gcc | ||
host-gcc | ||
linker_flags.cmake | ||
target.cmake | ||
target_baremetal.cmake | ||
target_base.cmake | ||
target_configure.cmake | ||
target_cpp.cmake | ||
target_relocation.cmake |