boost-dependency and generated pkg-config

[MartinSchwarzbauer]

Hi *!

We are using a boost dependency:
boost_dep = dependency('boost', modules: ['system', 'serialization', 'atomic', 'filesystem', 'thread'], required : true)

When generating a static library we use this dependency:

my_lib = static_library(
    'my_lib',
    sources: [...],
    include_directories : [...],
    dependencies: [boost_dep, ...],
    install: not(meson.is_subproject())
)

Everything works fine ... but the generated pkg-config confuses use:

[...]
Name: my_lib
Description: ...
Version: undefined
Requires: openssl
Libs: -L${libdir} -my_lib /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_serialization.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0 -pthread
Cflags: -I${includedir} -I/usr/include -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_USE_DLL=1 -DBOOST_ALL_NO_LIB -pthread

Why is the path absolute to all the single boost-modules? I expected.

This triggers a warning in yocto build too! How can i avoid this?
my_lib-1.0-r0 do_package_qa: QA Issue: File /usr/lib/pkgconfig/libmy_lib.pc in package my_lib-dev contains reference to TMPDIR [buildpaths]

[MartinSchwarzbauer]

Any comments?
Because these absolute path break our yocto build (caching troubles)! ... Is it possible to force boost dependencies entered not absolute in pkg-config file?