esp-idf/examples/system/unit_test/test/CMakeLists.txt

# This is the project CMakeLists.txt file for the test subproject
cmake_minimum_required(VERSION 3.5)

# Include the components directory of the main application:
#
set(EXTRA_COMPONENT_DIRS "../components")

# Set the components to include the tests for.
# This can be overriden from CMake cache:
# - when invoking CMake directly: cmake -D TEST_COMPONENTS="xxxxx" ..
# - when using idf.py: idf.py -T xxxxx build
#
set(TEST_COMPONENTS "testable" CACHE STRING "List of components to test")

include($ENV{IDF_PATH}/tools/cmake/project.cmake)
project(unit_test_test)
idf.py: Add support for action specific options Changes argument parsing mechanism from argparse to a new one, that provides better support for extensions and options that are only applicable to specific subcommands, Breaking changes: 1. All global options should go before subcommands, i.e. `idf.py build -C ~/some/project` will not work anymore, only `idf.py -C ~/some/project build` is acceptable 2. To provide multiple values to an option like `--define-cache-entry` it's necessary to repeat option many times, i.e. `idf.py -D entry1 entry2 entry3` will not work, right way is: `idf.py -D entry1 -D entry2 -D entry3` At the moment there are 3 options like this: `--define-cache-entry` in base list and `--test-components` and `--test-exclude-components` in the unit test extensions 3. Drops `defconfig` and `bootloader-clean` subcommands Closes https://github.com/espressif/esp-idf/issues/3570 Closes https://github.com/espressif/esp-idf/issues/3571 2019-04-10 18:06:52 +02:00			`# This is the project CMakeLists.txt file for the test subproject`
examples: add unit testing example 2018-10-25 20:31:35 +08:00			`cmake_minimum_required(VERSION 3.5)`

			`# Include the components directory of the main application:`
			`#`
			`set(EXTRA_COMPONENT_DIRS "../components")`

			`# Set the components to include the tests for.`
			`# This can be overriden from CMake cache:`
			`# - when invoking CMake directly: cmake -D TEST_COMPONENTS="xxxxx" ..`
idf.py: Add support for action specific options Changes argument parsing mechanism from argparse to a new one, that provides better support for extensions and options that are only applicable to specific subcommands, Breaking changes: 1. All global options should go before subcommands, i.e. `idf.py build -C ~/some/project` will not work anymore, only `idf.py -C ~/some/project build` is acceptable 2. To provide multiple values to an option like `--define-cache-entry` it's necessary to repeat option many times, i.e. `idf.py -D entry1 entry2 entry3` will not work, right way is: `idf.py -D entry1 -D entry2 -D entry3` At the moment there are 3 options like this: `--define-cache-entry` in base list and `--test-components` and `--test-exclude-components` in the unit test extensions 3. Drops `defconfig` and `bootloader-clean` subcommands Closes https://github.com/espressif/esp-idf/issues/3570 Closes https://github.com/espressif/esp-idf/issues/3571 2019-04-10 18:06:52 +02:00			`# - when using idf.py: idf.py -T xxxxx build`
examples: add unit testing example 2018-10-25 20:31:35 +08:00			`#`
			`set(TEST_COMPONENTS "testable" CACHE STRING "List of components to test")`

			`include($ENV{IDF_PATH}/tools/cmake/project.cmake)`
			`project(unit_test_test)`