RE: Compile part of a matter application as static library

mlampacher — Tue, 24 Sep 2024 10:15:28 GMT

Works for my current use-case, yes.

RE: Compile part of a matter application as static library

Amanda Hsieh — Mon, 23 Sep 2024 21:57:21 GMT

Hi,

Do you fix the issue?

-Amanda H.

RE: Compile part of a matter application as static library

mlampacher — Fri, 20 Sep 2024 09:11:03 GMT

After stumbling through include and linking order problems, this is what I've come up with.

cmake_minimum_required(VERSION 3.20.0)
set(CHIP_CFLAGS -DDUMMY_VALUE=0xDEADBEEF)

find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(
    Empty
    VERSION 0.1
    DESCRIPTION "empty matter application."
)
include(${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/config/nrfconnect/app/enable-gnu-std.cmake)
include(${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/src/app/chip_data_model.cmake)

set(zap_file    "${CMAKE_CURRENT_SOURCE_DIR}/src/zap/template.zap")
set(zap_gen_pwd "${CMAKE_CURRENT_SOURCE_DIR}/src")
set(zap_gen_dir "${zap_gen_pwd}/zap-generated")

target_sources(app PRIVATE src/main.cpp ...)
target_include_directories(app PRIVATE include src)

target_compile_options(
    app
    PRIVATE
    # TODO: required since i'm using Matter/CHIP in my "app" files too ...
    "-DCHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>"
)

add_library(app-chip OBJECT "")
target_include_directories(app-chip PRIVATE ${zap_gen_pwd})
target_link_libraries(
    app-chip
    PUBLIC
    zephyr
    chip
)

chip_configure_data_model(
    app-chip
    INCLUDE_SERVER
    BYPASS_IDL
    GEN_DIR ${zap_gen_dir}
    ZAP_FILE ${zap_file}
)

target_link_libraries(app PUBLIC app-chip)

Sadly, this doesn't help my use case since compiler errors are propagated through includes. And since C++ uses header files for implementation, and since I'm still using Matter/CHIP includes in my sources the compiler screams at me for stuff that I'm not responsible for (shadowed variables, unused parameters, etc.).

The cleanest solution would of course still be to separate the Matter/CHIP parts into a module or somehow else _completely_ decouple Matter/CHIP from other more strict implementation parts.