alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-09-19 14:26:01 -04:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
c392c06216
esp-idf/tools/mocks
History
Ivan Grokhotkov c392c06216
cmake: remove -D prefix from COMPILE_DEFINITIONS property 
Unlike COMPILE_OPTIONS, COMPILE_DEFINITIONS CMake property assumes
values without the -D prefix, such as NAME or NAME=VAL.
Previously, IDF build system was passing COMPILE_DEFINITIONS build
property to CMake COMPILE_OPTIONS property, so -D prefix was not
a problem.
Now that COMPILE_DEFINITIONS CMake property is used, -D prefix has
to be removed.

(Note that this doesn't affect 'target_compile_definitions' function,
which strips -D prefix before adding the definition to the property.)
2022-09-20 11:08:02 +02:00
..
driver cmake: remove -D prefix from COMPILE_DEFINITIONS property 2022-09-20 11:08:02 +02:00
esp_hw_support/include [mocks]: moved mocks dir to tools/ 2021-08-10 14:45:42 +08:00
esp_system/include [mocks]: moved mocks dir to tools/ 2021-08-10 14:45:42 +08:00
esp_timer [esp_timer]: created mock override component 2021-08-13 15:00:39 +08:00
freertos freertos: update freertos folder structure to match upstream 2021-10-29 12:05:13 +08:00
hal/include/hal gpio: Fix interrupt lost issue 2022-09-01 16:01:01 +08:00
soc/include/soc soc: don't expose unstable soc header files in public api 2022-01-06 23:10:22 +08:00
spi_flash spi_flash: Remove legacy spi_flash drivers 2022-07-01 11:01:34 +08:00
README.md [mocks]: moved mocks dir to tools/ 2021-08-10 14:45:42 +08:00

README.md

Mocked Components

All components in this directory mock their respective originals in the component directory. The components in this directory are for testing only. Currently, the main goal is to implement Linux-based host tests with these mocking components. Target-based tests using the mocking components are not possible now but may be possible in the future.

Some components only consist of header files without any CMakeLists.txt file. The headers in these are currently needed by other mocking components to satisfy a minimal set of definitions from dependencies. They are not a full mock implementation. These components with header files only may be replaced by an actual mock implementation of the corresponding component in the future.