James

That is weird, the files should be right there in your folder. You can add the ``--deployer-folder=myruntimefolder`` to explicitly define a folder name for the output. Are you sure that...

> if I run the command by hand in the terminal I see the DLLs and everything works as expected! Interesting, thanks for the feedback! So it seems this would...

Hi @nine Thanks for your question. The reason is that the propagation of headers of ``nlohman_json`` stops by default at ``lib_b``. Unless it also defines ``transitive_headers=True``, the headers will not...

Thanks for the feedback. The solution is still the same, it requires ``transitive_headers=True`` in each package recipe. This is because the headers transitivity is a property of every package recipe,...

Hi @nine Any comment or feedback about the last response? Thanks!

Thanks for your feedback. Now I understand better that you have a very specific build system with some target definition and propagation that is not the conventional one, and that...

> But sometimes users need to split 3rd-party install config and project build config. Like I want to use release 3rd-party install config for all project build configs. In this...

Thanks for the details to reproduce, that helps to understand it. It seems you are missing in your ``CMakeLists.txt``: ```cmake set(CMAKE_MAP_IMPORTED_CONFIG_RELWITHDEBINFO Release) ... ``` This is likely it won't be...

Hi @tkielan Thanks for your feedback. The ``conan_cmake_install`` refers to the legacy Conan 1.X integration. Conan 1.X is deprecated and no longer maintained, Conan 2 has been there for 2...

Yes, of course, the one in this repo. It is using the CMake dependency providers, the instructions are in the main readme: https://github.com/conan-io/cmake-conan