Hi @BastienGermond! It seems that there are two different aspects here:

1. The place where the generated mock implementations are placed.
2. Problems including the correct header files.

Do you have problems with both or just one of these aspects?
Regarding 1.: Usually, it shouldn't matter where the source files (*.c) are placed, the includes are absolute paths. Furthermore, the IDF build system should take care of setting up the compiler calls so all source files are found. Do you have source files with the same name which would conflict with each other after the mocks have been generated?
Regarding 2.: This should also work as long as the include directories are set in the CMakeLists.txt of your mocking component (the one that is creating the mocks).

Hi @0xjakob,

1. The place where the generated mock implementations are placed.

The issue is that the files generated with the cmock_configuration :subdir: myproject would be created in this path ${MOCK_GEN_DIR}/mocks/myproject/Mock${file_without_dir}.[ch].

What I'm trying to say is that currently the path is hardcoded expecting the default values from CMock (:subdir: "", :mock_path: "mocks" and :mock_prefix: "Mock").

In case we have a mock_config.yaml like this :

:cmock:
  :subdir: "myproject"
  :mock_prefix: "Espressif"
  :mock_path: "EspMocks"
  :plugins:
    - :ignore
    - :callback

This would generate files following this path : ${MOCK_GEN_DIR}/EspMocks/myproject/Espressif${file_without_dir}.[ch]

the IDF build system should take care of setting up the compiler calls so all source files are found.

And because of this different path the c-files are not registered correctly (and thus not found/compiled during compilation causing missing symbols during linking).

2. Problems including the correct header files.

I also have this problem caused by not using :subdir, in my project I use a #include "myproject/nvs.h" but generating mocks for this without subdir will include "nvs.h" and not the expected "myproject/nvs.h" in Mocknvs.h.

I patched it the first time the same way esp-idf does for freertos with adding manually my correct header with :includes_h_pre_orig_header.

CMock still add an #include "nvs.h" in the mock header generated but at least this added afterward the correct #include "myproject/nvs.h".

However, in case the "nvs.h" was not something found in any include path or something that is not wanted in this header, the compilation will fail with an include not found error or maybe collide with the right header (myproject/nvs.h).

I apologize if my explanation was unclear. Please let me know if you did not catch what I mean and I will try to rephrase it 😄.

It starts to make much more sense now, thanks! Supporting :subdir: makes sense then, in particular because of the includes.

Regarding support for custom :mock_path: and :mock_dir:: I think we could also add that option, although I don't quite understand why they are necessary. Taking :subdir: aside, is there a situation where you have a custom :mock_path: or :mock_prefix: configured in IDF?

Taking :subdir: aside, is there a situation where you have a custom :mock_path: or :mock_prefix: configured in IDF?

Not really, and I agree that I don't see a use case right now. Maybe some company may have some convention about filename enforced by tools ?

I was mentioning them only since they will not work with the current process, the real issue for me was the missing :subdir support.