esp-idf/tools/mocks
Darian Leung 66499f17a5 freertos: Refactor component structure
This commit refactors the "freertos" component's structure as follows:

- "FreeRTOSConfig.h" related files moved to "./config" directory
- Refactored CMakeLists.txt file in preparation for v10.5.1 upgrade
    - Grouped list appends based on component organization
    - Removed some unecessarily public "include_dirs"
- Removed FreeRTOS-openocd.c
    - uxTopUsedPriority has been added back to tasks.c since v10.4.2
    - Thus the workaround in FreeRTOS-openocd.c is no longer needed and can
      be removed.
2023-05-08 18:40:03 +08:00
..
driver feat(driver): added RMT mock 2023-03-17 14:54:48 +08:00
esp-tls [tcp_transport] - Adds Socks4 proxy transport 2023-03-27 14:46:40 +02:00
esp_event
esp_hw_support systimer: support etm event 2022-11-23 15:32:34 +08:00
esp_partition Storage: Partition APIs moved to the new component 'esp_partition' 2022-11-02 21:54:45 +01:00
esp_timer systimer: support etm event 2022-11-23 15:32:34 +08:00
freertos freertos: Refactor component structure 2023-05-08 18:40:03 +08:00
hal/include/hal feat(driver): added RMT mock 2023-03-17 14:54:48 +08:00
http_parser
lwip [tcp_transport] - Adds Socks4 proxy transport 2023-03-27 14:46:40 +02:00
soc/include/soc linux target: add support for building esp_hw_support, soc and hal components for linux target 2022-12-09 13:59:39 +08:00
spi_flash Storage: Partition APIs moved to the new component 'esp_partition' 2022-11-02 21:54:45 +01:00
startup lwip: Support for linux target 2023-01-31 08:43:45 +01:00
tcp_transport
README.md

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.