alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
bd40793771
esp-idf/tools/ci/test_build_system_cmake.sh

1143 lines
56 KiB
Bash
Raw Normal View History

ci: use default Bash version in macOS test
2020-04-07 03:50:59 -04:00
#!/bin/bash
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
#
# Test the build system for basic consistency (Cmake/idf.py version)
#
# A bash script that tests some likely build failure scenarios in a row
#
# Assumes PWD is an out-of-tree build directory, and will create a
# subdirectory inside it to run build tests in.
#
# Environment variables:
# IDF_PATH - must be set
# ESP_IDF_TEMPLATE_GIT - Can override git clone source for template app. Otherwise github.
# NOCLEANUP - Set to '1' if you want the script to leave its temporary directory when done, for post-mortem.
#
#
# Internals:
# * The tests run in sequence & the system keeps track of all failures to print at the end.
# * BUILD directory is set to default BUILD_DIR_BASE
# * The "print_status" function both prints a status line to the log and keeps track of which test is running.
# * Calling the "failure" function prints a failure message to the log and also adds to the list of failures to print at the end.
# * The function "assert_built" tests for a file relative to the BUILD directory.
# * The function "take_build_snapshot" can be paired with the functions "assert_rebuilt" and "assert_not_rebuilt" to compare file timestamps and verify if they were rebuilt or not since the snapshot was taken.
#
# To add a new test case, add it to the end of the run_tests function. Note that not all test cases do comprehensive cleanup
# (although very invasive ones like appending CRLFs to all files take a copy of the esp-idf tree), however the clean_build_dir
# function can be used to force-delete all files from the build output directory.
# Set up some variables
#
# override ESP_IDF_TEMPLATE_GIT to point to a local dir if you're testing and want fast iterations
[ -z ${ESP_IDF_TEMPLATE_GIT} ] && ESP_IDF_TEMPLATE_GIT=https://github.com/espressif/esp-idf-template.git
# uncomment next line to produce a lot more debug output
#export V=1
export PATH="$IDF_PATH/tools:$PATH" # for idf.py
ci: disable ccache when running CMake build system tests Some tests check if certain files are rebuilt when source files are 'touch'ed. With ccache, 'touch'ing source files doesn't cause a rebuild, hence the test fails. In case IDF_CCACHE_ENABLE was set in the environment, unset it before starting the tests.
2021-11-05 10:13:30 -04:00
# Some tests assume that ccache is not enabled
unset IDF_CCACHE_ENABLE
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
function run_tests()
{
FAILURES=
STATUS="Starting"
print_status "Checking prerequisites"
[ -z ${IDF_PATH} ] && echo "IDF_PATH is not set. Need path to esp-idf installation." && exit 2
print_status "Cloning template from ${ESP_IDF_TEMPLATE_GIT}..."
git clone ${ESP_IDF_TEMPLATE_GIT} template
cd template
ci: Allow bot to control branch used for esp-idf-template
2018-05-08 02:42:54 -04:00
if [ -z $CHECKOUT_REF_SCRIPT ]; then
git checkout ${CI_BUILD_REF_NAME} || echo "Using esp-idf-template default branch..."
else
ci: fix test build system when using template repository from a different branch then master
2019-09-09 05:48:24 -04:00
$CHECKOUT_REF_SCRIPT esp-idf-template .
ci: Allow bot to control branch used for esp-idf-template
2018-05-08 02:42:54 -04:00
fi
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "Try to clean fresh directory..."
idf.py fullclean || exit $?
# all relative to the build directory
BOOTLOADER_BINS="bootloader/bootloader.elf bootloader/bootloader.bin"
APP_BINS="app-template.elf app-template.bin"
PARTITION_BIN="partition_table/partition-table.bin"
esp_wifi: fix wrong path of phy_init_data Closes https://github.com/espressif/esp-idf/issues/3482
2019-06-11 23:52:23 -04:00
PHY_INIT_BIN="phy_init_data.bin"
cmake: restore creation of kconfig_menus.json
2019-05-23 06:08:22 -04:00
BUILD_ARTIFACTS="project_description.json flasher_args.json config/kconfig_menus.json config/sdkconfig.json"
examples: update with build system changes
2019-04-26 05:51:48 -04:00
IDF_COMPONENT_PREFIX="__idf"
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "Initial clean build"
# if build fails here, everything fails
idf.py build || exit $?
# check all the expected build artifacts from the clean build
cmake: restore creation of kconfig_menus.json
2019-05-23 06:08:22 -04:00
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN} ${BUILD_ARTIFACTS}
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "Updating component source file rebuilds component"
# touch a file & do a build
take_build_snapshot
ci: update build system tests
2020-03-03 01:29:39 -05:00
touch ${IDF_PATH}/components/esp_system/port/cpu_start.c
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
idf.py build || failure "Failed to partial build"
docs: fix build issue requiring new location of cpu_start.c
2020-03-03 01:31:50 -05:00
assert_rebuilt ${APP_BINS} esp-idf/esp_system/libesp_system.a esp-idf/esp_system/CMakeFiles/${IDF_COMPONENT_PREFIX}_esp_system.dir/port/cpu_start.c.obj
ci: update for running cmake examples
2018-11-07 02:19:56 -05:00
assert_not_rebuilt esp-idf/lwip/liblwip.a esp-idf/freertos/libfreertos.a ${BOOTLOADER_BINS} ${PARTITION_BIN}
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "Bootloader source file rebuilds bootloader"
take_build_snapshot
touch ${IDF_PATH}/components/bootloader/subproject/main/bootloader_start.c
idf.py build || failure "Failed to partial build bootloader"
ci: update for running cmake examples
2018-11-07 02:19:56 -05:00
assert_rebuilt ${BOOTLOADER_BINS} bootloader/esp-idf/main/CMakeFiles/${IDF_COMPONENT_PREFIX}_main.dir/bootloader_start.c.obj
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
assert_not_rebuilt ${APP_BINS} ${PARTITION_BIN}
print_status "Partition CSV file rebuilds partitions"
take_build_snapshot
touch ${IDF_PATH}/components/partition_table/partitions_singleapp.csv
idf.py build || failure "Failed to build partition table"
assert_rebuilt ${PARTITION_BIN}
assert_not_rebuilt app-template.bin app-template.elf ${BOOTLOADER_BINS}
print_status "Partial build doesn't compile anything by default"
take_build_snapshot
# verify no build files are refreshed by a partial make
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
ALL_BUILD_FILES=$(find ${BUILD} -type f | ${SED} "s@${BUILD}/@@" | grep -v '^.')
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
idf.py build || failure "Partial build failed"
assert_not_rebuilt ${ALL_BUILD_FILES}
esp32: Add firmware version to app Added a new structure esp_app_desc_t. It has info about firmware: version, secure_version, project_name, time/date build and IDF version. Added the ability to add a custom structure with a description of the firmware. The esp_app_desc_t is located in fixed place in start of ROM secotor. It is located after structures esp_image_header_t and esp_image_segment_header_t. app_version is filed from PROJECT_VER variable (if set in custom make file) or PROJECT_PATH/version.txt or git repo (git describe). Add API to get app_desc from partition.
2018-10-05 08:29:07 -04:00
print_status "Rebuild when app version was changed"
clean_build_dir
# App version
tools/test_build_system: Add tests with long IDF_VER
2019-03-13 08:43:33 -04:00
echo "IDF_VER_0123456789_0123456789_0123456789" > ${IDF_PATH}/version.txt
esp32: Add firmware version to app Added a new structure esp_app_desc_t. It has info about firmware: version, secure_version, project_name, time/date build and IDF version. Added the ability to add a custom structure with a description of the firmware. The esp_app_desc_t is located in fixed place in start of ROM secotor. It is located after structures esp_image_header_t and esp_image_segment_header_t. app_version is filed from PROJECT_VER variable (if set in custom make file) or PROJECT_PATH/version.txt or git repo (git describe). Add API to get app_desc from partition.
2018-10-05 08:29:07 -04:00
echo "project-version-1.0" > ${TESTDIR}/template/version.txt
idf.py build || failure "Failed to build with app version"
print_status "Change app version"
take_build_snapshot
build: Add trimming PROJECT_VER and PROJECT_NAME vars
2018-12-07 11:23:44 -05:00
echo "project-version-2.0(012345678901234567890123456789)" > ${TESTDIR}/template/version.txt
esp32: Add firmware version to app Added a new structure esp_app_desc_t. It has info about firmware: version, secure_version, project_name, time/date build and IDF version. Added the ability to add a custom structure with a description of the firmware. The esp_app_desc_t is located in fixed place in start of ROM secotor. It is located after structures esp_image_header_t and esp_image_segment_header_t. app_version is filed from PROJECT_VER variable (if set in custom make file) or PROJECT_PATH/version.txt or git repo (git describe). Add API to get app_desc from partition.
2018-10-05 08:29:07 -04:00
idf.py build || failure "Failed to rebuild with changed app version"
assert_rebuilt ${APP_BINS}
ci: update build system tests
2020-03-03 01:29:39 -05:00
assert_not_rebuilt ${BOOTLOADER_BINS} esp-idf/esp_system/libesp_system.a
cmake: add spaces2list for COMPONENT_SRCS According to ESP-IDF Cmake build system document, COMPONENT_SRCS should support using spaces to sperate source files. Closes https://github.com/espressif/esp-idf/issues/3130
2019-03-05 23:18:38 -05:00
tools: Add unit tests
2019-01-23 07:27:28 -05:00
print_status "Re-building does not change app.bin"
take_build_snapshot
idf.py build
ci: update build system tests
2020-03-03 01:29:39 -05:00
assert_not_rebuilt ${APP_BINS} ${BOOTLOADER_BINS} esp-idf/esp_system/libesp_system.a
tools/test_build_system: Add tests with long IDF_VER
2019-03-13 08:43:33 -04:00
rm -f ${IDF_PATH}/version.txt
esp32: Add firmware version to app Added a new structure esp_app_desc_t. It has info about firmware: version, secure_version, project_name, time/date build and IDF version. Added the ability to add a custom structure with a description of the firmware. The esp_app_desc_t is located in fixed place in start of ROM secotor. It is located after structures esp_image_header_t and esp_image_segment_header_t. app_version is filed from PROJECT_VER variable (if set in custom make file) or PROJECT_PATH/version.txt or git repo (git describe). Add API to get app_desc from partition.
2018-10-05 08:29:07 -04:00
rm -f ${TESTDIR}/template/version.txt
cmake: add spaces2list for COMPONENT_SRCS According to ESP-IDF Cmake build system document, COMPONENT_SRCS should support using spaces to sperate source files. Closes https://github.com/espressif/esp-idf/issues/3130
2019-03-05 23:18:38 -05:00
tools: Add unit tests
2019-01-23 07:27:28 -05:00
print_status "Get the version of app from git describe. Project is not inside IDF and do not have a tag only a hash commit."
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
idf.py reconfigure >> log.log || failure "Failed to build"
build: Add CONFIG_APP_PROJECT_VER to set the project version from Kconfig
2019-11-27 06:01:40 -05:00
version="App \"app-template\" version: "
tools: Add unit tests
2019-01-23 07:27:28 -05:00
version+=$(git describe --always --tags --dirty)
grep "${version}" log.log || failure "Project version should have a hash commit"
build: Add CONFIG_APP_PROJECT_VER to set the project version from Kconfig
2019-11-27 06:01:40 -05:00
print_status "Get the version of app from Kconfig option"
idf.py clean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
echo "project_version_from_txt" > ${TESTDIR}/template/version.txt
echo "CONFIG_APP_PROJECT_VER_FROM_CONFIG=y" >> sdkconfig.defaults
echo 'CONFIG_APP_PROJECT_VER="project_version_from_Kconfig"' >> sdkconfig.defaults
idf.py build >> log.log || failure "Failed to build"
version="App \"app-template\" version: "
version+="project_version_from_Kconfig"
grep "${version}" log.log || failure "Project version should be from Kconfig"
rm -f sdkconfig.defaults
rm -f sdkconfig
rm -f ${TESTDIR}/template/version.txt
cmake: set IDF_VERSION_* variables at requirement expansion stage Currently IDF_VERSION_* variables are not available to the component CMakeLists.txt files at the requirements expansion stage. This makes it harder to write component CMakeLists files compatible with different IDF versions. Include version.cmake from the requirements expansion script, add a build system test.
2020-12-15 14:53:19 -05:00
print_status "Use IDF version variables in component CMakeLists.txt file"
clean_build_dir
(echo -e "if (NOT IDF_VERSION_MAJOR)\n message(FATAL_ERROR \"IDF version not set\")\n endif()" \
&& cat main/CMakeLists.txt) > main/CMakeLists.new && mv main/CMakeLists.new main/CMakeLists.txt
idf.py reconfigure || failure "Failed to use IDF_VERSION_MAJOR in component CMakeLists.txt"
git checkout -- main/CMakeLists.txt
tools: Use git describe --match for filtering out internal names
2021-02-17 08:04:04 -05:00
print_status "Project is in ESP-IDF which has a custom tag"
pushd ${IDF_PATH}/examples/get-started/hello_world
CI: Fix git tag in cmake build tests where email address cannot be autodetected
2021-03-11 07:37:58 -05:00
GIT_COMMITTER_NAME="No One" GIT_COMMITTER_EMAIL="noone@espressif.com" git tag mytag -a -m "mytag" || failure "Git cannot create tag"
tools: Use git describe --match for filtering out internal names
2021-02-17 08:04:04 -05:00
idf.py reconfigure &> log.log || failure "Failed to build"
[examples]: removed hyphens Replaced hyphens with underscores in examples project definition for all examples which had hyphens in their project name. dpp-enrollee is an exceptions because the name matches the project directory name while the project directory also contains hyphens.
2021-07-05 02:33:56 -04:00
str="App \"hello_world\" version: mytag"
tools: Use git describe --match for filtering out internal names
2021-02-17 08:04:04 -05:00
grep "${str}" log.log || { cat log.log ; failure "Project version should be the custom tag"; }
idf_version=$(idf.py --version)
if [[ "$idf_version" == *"mytag"* ]]; then
failure "IDF version $idf_version should not contain mytag"
fi
git tag -d mytag
CI: Fix git tag in cmake build tests where email address cannot be autodetected
2021-03-11 07:37:58 -05:00
rm -rf sdkconfig build
tools: Use git describe --match for filtering out internal names
2021-02-17 08:04:04 -05:00
popd
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "Moving BUILD_DIR_BASE out of tree"
clean_build_dir
OUTOFTREE_BUILD=${TESTDIR}/alt_build
idf.py -B "${OUTOFTREE_BUILD}" build || failure "Failed to build with out-of-tree build dir"
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
NEW_BUILD_FILES=$(find ${OUTOFTREE_BUILD} -type f)
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
if [ -z "${NEW_BUILD_FILES}" ]; then
failure "No files found in new build directory!"
fi
DEFAULT_BUILD_FILES=$(find ${BUILD} -mindepth 1)
if [ -n "${DEFAULT_BUILD_FILES}" ]; then
failure "Some files were incorrectly put into the default build directory: ${DEFAULT_BUILD_FILES}"
fi
print_status "BUILD_DIR_BASE inside default build directory"
clean_build_dir
idf.py -B "build/subdirectory" build || failure "Failed to build with build dir as subdir"
NEW_BUILD_FILES=$(find ${BUILD}/subdirectory -type f)
if [ -z "${NEW_BUILD_FILES}" ]; then
failure "No files found in new build directory!"
fi
print_status "Can still clean build if all text files are CRLFs"
clean_build_dir
find . -path .git -prune -exec unix2dos {} \; # CRLFify template dir
# make a copy of esp-idf and CRLFify it
CRLF_ESPIDF=${TESTDIR}/esp-idf-crlf
mkdir -p ${CRLF_ESPIDF}
ci: fix regression in build system tests On macOS, rsync --exclude option accepts absolute paths as well as relative ones. On Linux, it doesn't, which results in endless recursive copying of test_build_system directory.
2019-11-01 10:43:21 -04:00
TESTDIR_REL=$($REALPATH ${TESTDIR} --relative-to ${IDF_PATH})
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
# Note: trailing slash after ${IDF_PATH} avoids creating esp-idf directory inside ${CRLF_ESPIDF}
ci: fix regression in build system tests On macOS, rsync --exclude option accepts absolute paths as well as relative ones. On Linux, it doesn't, which results in endless recursive copying of test_build_system directory.
2019-11-01 10:43:21 -04:00
rsync -a --exclude ${TESTDIR_REL} ${IDF_PATH}/ ${CRLF_ESPIDF}
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
# don't CRLFify executable files, as Linux will fail to execute them
find ${CRLF_ESPIDF} -name .git -prune -name build -prune -type f ! -perm 755 -exec unix2dos {} \;
IDF_PATH=${CRLF_ESPIDF} idf.py build || failure "Failed to build with CRLFs in source"
# do the same checks we do for the clean build
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
print_status "Updating rom ld file should re-link app and bootloader"
clean_build_dir
idf.py build
take_build_snapshot
sleep 1 # ninja may ignore if the timestamp delta is too low
separate rom from esp32 component to esp_rom 1. separate rom include files and linkscript to esp_rom 2. modefiy "include rom/xxx.h" to "include esp32/rom/xxx.h" 3. Forward compatible 4. update mqtt
2019-03-14 05:29:32 -04:00
cp ${IDF_PATH}/components/esp_rom/esp32/ld/esp32.rom.ld .
echo "/* (Build test comment) */" >> ${IDF_PATH}/components/esp_rom/esp32/ld/esp32.rom.ld
tail ${IDF_PATH}/components/esp_rom/esp32/ld/esp32.rom.ld
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
idf.py build || failure "Failed to rebuild with modified linker script"
assert_rebuilt ${APP_BINS} ${BOOTLOADER_BINS}
separate rom from esp32 component to esp_rom 1. separate rom include files and linkscript to esp_rom 2. modefiy "include rom/xxx.h" to "include esp32/rom/xxx.h" 3. Forward compatible 4. update mqtt
2019-03-14 05:29:32 -04:00
mv esp32.rom.ld ${IDF_PATH}/components/esp_rom/esp32/ld/
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "Updating app-only ld file should only re-link app"
take_build_snapshot
esp32: move app linker scripts
2021-04-07 22:27:21 -04:00
cp ${IDF_PATH}/components/esp_system/ld/esp32/sections.ld.in .
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
sleep 1 # ninja may ignore if the timestamp delta is too low
esp32: move app linker scripts
2021-04-07 22:27:21 -04:00
echo "/* (Build test comment) */" >> ${IDF_PATH}/components/esp_system/ld/esp32/sections.ld.in
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
idf.py build || failure "Failed to rebuild with modified linker script"
assert_rebuilt ${APP_BINS}
assert_not_rebuilt ${BOOTLOADER_BINS}
esp32: move app linker scripts
2021-04-07 22:27:21 -04:00
mv sections.ld.in ${IDF_PATH}/components/esp_system/ld/esp32
tools: implement linker script generation
2018-04-17 22:57:45 -04:00
build: fix linker scripts edition not triggering a rebuild Fix the dependencies in CMakeLists files for triggering a relink when linker script file is modified.
2021-02-28 23:30:50 -05:00
print_status "Updating ld file should only re-link app"
take_build_snapshot
esp32: move app linker scripts
2021-04-07 22:27:21 -04:00
cp ${IDF_PATH}/components/esp_system/ld/esp32/memory.ld .
build: fix linker scripts edition not triggering a rebuild Fix the dependencies in CMakeLists files for triggering a relink when linker script file is modified.
2021-02-28 23:30:50 -05:00
sleep 1 # ninja may ignore if the timestamp delta is too low
esp32: move app linker scripts
2021-04-07 22:27:21 -04:00
echo "/* (Build test comment) */" >> ${IDF_PATH}/components/esp_system/ld/esp32/memory.ld.in
build: fix linker scripts edition not triggering a rebuild Fix the dependencies in CMakeLists files for triggering a relink when linker script file is modified.
2021-02-28 23:30:50 -05:00
idf.py build || failure "Failed to rebuild with modified linker script"
assert_rebuilt ${APP_BINS}
assert_not_rebuilt ${BOOTLOADER_BINS}
esp32: move app linker scripts
2021-04-07 22:27:21 -04:00
mv memory.ld ${IDF_PATH}/components/esp_system/ld/esp32/
build: fix linker scripts edition not triggering a rebuild Fix the dependencies in CMakeLists files for triggering a relink when linker script file is modified.
2021-02-28 23:30:50 -05:00
tools: implement linker script generation
2018-04-17 22:57:45 -04:00
print_status "Updating fragment file should only re-link app" # only app linker script is generated by tool for now
take_build_snapshot
esp32: move common fragment definitions
2021-03-10 06:33:24 -05:00
cp ${IDF_PATH}/components/esp_common/common.lf .
tools: implement linker script generation
2018-04-17 22:57:45 -04:00
sleep 1 # ninja may ignore if the timestamp delta is too low
esp32: move common fragment definitions
2021-03-10 06:33:24 -05:00
echo "# (Build test comment)" >> ${IDF_PATH}/components/esp_common/common.lf
tools: implement linker script generation
2018-04-17 22:57:45 -04:00
idf.py build || failure "Failed to rebuild with modified linker fragment file"
assert_rebuilt ${APP_BINS}
assert_not_rebuilt ${BOOTLOADER_BINS}
esp32: move common fragment definitions
2021-03-10 06:33:24 -05:00
mv common.lf ${IDF_PATH}/components/esp_common
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "sdkconfig update triggers full recompile"
clean_build_dir
idf.py build
take_build_snapshot
# need to actually change config, or cmake is too smart to rebuild
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
${SED} -i.bak s/^\#\ CONFIG_FREERTOS_UNICORE\ is\ not\ set/CONFIG_FREERTOS_UNICORE=y/ sdkconfig
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
idf.py build
# check the sdkconfig.h file was rebuilt
cmake build system test: Fix path to sdkconfig.h
2018-05-30 23:31:42 -04:00
assert_rebuilt config/sdkconfig.h
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
# pick one each of .c, .cpp, .S that #includes sdkconfig.h
# and therefore should rebuild
newlib: Update esp32c3 ROM support, use single init function
2020-12-29 20:31:16 -05:00
assert_rebuilt esp-idf/newlib/CMakeFiles/${IDF_COMPONENT_PREFIX}_newlib.dir/newlib_init.c.obj
ci: update for running cmake examples
2018-11-07 02:19:56 -05:00
assert_rebuilt esp-idf/nvs_flash/CMakeFiles/${IDF_COMPONENT_PREFIX}_nvs_flash.dir/src/nvs_api.cpp.obj
freertos: update freertos folder structure to match upstream The following changes have been made: 1. All FreeRTOS kernel source files are now placed in the freertos/FreeRTOS-Kernel folder to match with the upstream folder structure. 2. All kernel include files are now placed in freertos/FreeRTOS-Kernel/include. 3. All port files are now placed in freertos/FreeRTOS-Kernel/portable. 4. All additions/customizations are placed in freertos/esp_additions. 5. All other miscellaneous files (README, License files etc.) are moved to freertos/FreeRTOS-Kernel folder to match with the upstream. 6. Updated esp-cryptoauthlib to latest commit to resolve FreeRTOS include dependencies. Signed-off-by: Sudeep Mohanty <sudeep.mohanty@espressif.com>
2021-09-20 02:07:03 -04:00
assert_rebuilt esp-idf/freertos/CMakeFiles/${IDF_COMPONENT_PREFIX}_freertos.dir/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S.obj
build example tests: Use portable "sed -i" form
2018-12-05 23:14:59 -05:00
mv sdkconfig.bak sdkconfig
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "Updating project CMakeLists.txt triggers full recompile"
clean_build_dir
idf.py build
take_build_snapshot
# Need to actually change the build config, or CMake won't do anything
cmake: Fix issues when IDF_PATH is not set in environment Support cases where IDF_PATH may be passed in on the cmake command line, or inferred from a (hardcoded absolute or relative) path to project.cmake
2018-06-15 00:59:45 -04:00
cp CMakeLists.txt CMakeLists.bak
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
${SED} -i.bak 's/^project(/add_compile_options("-DUSELESS_MACRO_DOES_NOTHING=1")\nproject\(/' CMakeLists.txt
cmake: Fix issues when IDF_PATH is not set in environment Support cases where IDF_PATH may be passed in on the cmake command line, or inferred from a (hardcoded absolute or relative) path to project.cmake
2018-06-15 00:59:45 -04:00
idf.py build || failure "Build failed"
mv CMakeLists.bak CMakeLists.txt
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
# similar to previous test
newlib: Update esp32c3 ROM support, use single init function
2020-12-29 20:31:16 -05:00
assert_rebuilt esp-idf/newlib/CMakeFiles/${IDF_COMPONENT_PREFIX}_newlib.dir/newlib_init.c.obj
ci: update for running cmake examples
2018-11-07 02:19:56 -05:00
assert_rebuilt esp-idf/nvs_flash/CMakeFiles/${IDF_COMPONENT_PREFIX}_nvs_flash.dir/src/nvs_api.cpp.obj
freertos: update freertos folder structure to match upstream The following changes have been made: 1. All FreeRTOS kernel source files are now placed in the freertos/FreeRTOS-Kernel folder to match with the upstream folder structure. 2. All kernel include files are now placed in freertos/FreeRTOS-Kernel/include. 3. All port files are now placed in freertos/FreeRTOS-Kernel/portable. 4. All additions/customizations are placed in freertos/esp_additions. 5. All other miscellaneous files (README, License files etc.) are moved to freertos/FreeRTOS-Kernel folder to match with the upstream. 6. Updated esp-cryptoauthlib to latest commit to resolve FreeRTOS include dependencies. Signed-off-by: Sudeep Mohanty <sudeep.mohanty@espressif.com>
2021-09-20 02:07:03 -04:00
assert_rebuilt esp-idf/freertos/CMakeFiles/${IDF_COMPONENT_PREFIX}_freertos.dir/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S.obj
build example tests: Use portable "sed -i" form
2018-12-05 23:14:59 -05:00
mv sdkconfig.bak sdkconfig
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
cmake: Fix issues when IDF_PATH is not set in environment Support cases where IDF_PATH may be passed in on the cmake command line, or inferred from a (hardcoded absolute or relative) path to project.cmake
2018-06-15 00:59:45 -04:00
print_status "Can build with Ninja (no idf.py)"
clean_build_dir
(cd build && cmake -G Ninja .. && ninja) || failure "Ninja build failed"
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
print_status "Can build with GNU Make (no idf.py)"
clean_build_dir
mkdir build
(cd build && cmake -G "Unix Makefiles" .. && make) || failure "Make build failed"
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
tools: fix idf.py to be able to select a generator for build
2020-03-05 08:53:47 -05:00
print_status "idf.py can build with Ninja"
clean_build_dir
idf.py -G Ninja build || failure "idf.py cannot build with Ninja"
grep "CMAKE_GENERATOR:INTERNAL=Ninja" build/CMakeCache.txt || failure "Ninja is not set in CMakeCache.txt"
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
print_status "idf.py can build with Unix Makefiles"
clean_build_dir
mkdir build
idf.py -G "Unix Makefiles" build || failure "idf.py cannot build with Unix Makefiles"
grep "CMAKE_GENERATOR:INTERNAL=Unix Makefiles" build/CMakeCache.txt || failure "Unix Makefiles are not set in CMakeCache.txt"
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
cmake: Fix issues when IDF_PATH is not set in environment Support cases where IDF_PATH may be passed in on the cmake command line, or inferred from a (hardcoded absolute or relative) path to project.cmake
2018-06-15 00:59:45 -04:00
print_status "Can build with IDF_PATH set via cmake cache not environment"
clean_build_dir
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
${SED} -i.bak 's/ENV{IDF_PATH}/{IDF_PATH}/' CMakeLists.txt
cmake: Fix issues when IDF_PATH is not set in environment Support cases where IDF_PATH may be passed in on the cmake command line, or inferred from a (hardcoded absolute or relative) path to project.cmake
2018-06-15 00:59:45 -04:00
export IDF_PATH_BACKUP="$IDF_PATH"
(unset IDF_PATH &&
cd build &&
cmake -G Ninja .. -DIDF_PATH=${IDF_PATH_BACKUP} &&
ninja) || failure "Ninja build failed"
build example tests: Use portable "sed -i" form
2018-12-05 23:14:59 -05:00
mv CMakeLists.txt.bak CMakeLists.txt
cmake: Fix issues when IDF_PATH is not set in environment Support cases where IDF_PATH may be passed in on the cmake command line, or inferred from a (hardcoded absolute or relative) path to project.cmake
2018-06-15 00:59:45 -04:00
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
print_status "Can build with IDF_PATH unset and inferred by build system"
clean_build_dir
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
${SED} -i.bak "s%\$ENV{IDF_PATH}%\${ci_idf_path}%" CMakeLists.txt # expand to a hardcoded path
ci: fix build test with IDF_PATH unset on Windows
2018-12-11 03:00:28 -05:00
(ci_idf_path=${IDF_PATH} && unset IDF_PATH && cd build &&
cmake -G Ninja -D ci_idf_path=${ci_idf_path} .. && ninja) || failure "Ninja build failed"
build example tests: Use portable "sed -i" form
2018-12-05 23:14:59 -05:00
mv CMakeLists.txt.bak CMakeLists.txt
cmake: Fix issues when IDF_PATH is not set in environment Support cases where IDF_PATH may be passed in on the cmake command line, or inferred from a (hardcoded absolute or relative) path to project.cmake
2018-06-15 00:59:45 -04:00
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
CMake: Make IDF_PATH available to Kconfiglib when not explicitly set. When IDF_PATH is not set by the user, cmake infers the same through other means and sets it as an environment variable. However, some sub-invocation of cmake may not see this variable as it is not set in the parent. This change adds a custom command for exporting IDF_PATH just before invoking ldgen so that IDF_PATH can be used in Kconfig without any errors.
2019-01-11 01:29:59 -05:00
print_status "Can build with IDF_PATH unset and inferred by cmake when Kconfig needs it to be set"
clean_build_dir
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
${SED} -i.bak 's/ENV{IDF_PATH}/{IDF_PATH}/' CMakeLists.txt
CMake: Make IDF_PATH available to Kconfiglib when not explicitly set. When IDF_PATH is not set by the user, cmake infers the same through other means and sets it as an environment variable. However, some sub-invocation of cmake may not see this variable as it is not set in the parent. This change adds a custom command for exporting IDF_PATH just before invoking ldgen so that IDF_PATH can be used in Kconfig without any errors.
2019-01-11 01:29:59 -05:00
export IDF_PATH_BACKUP="$IDF_PATH"
mv main/Kconfig.projbuild main/Kconfig.projbuild_bak
echo "source \"\$IDF_PATH/examples/wifi/getting_started/station/main/Kconfig.projbuild\"" > main/Kconfig.projbuild
(unset IDF_PATH &&
cd build &&
cmake -G Ninja .. -DIDF_PATH=${IDF_PATH_BACKUP} &&
ninja) || failure "Ninja build failed"
mv CMakeLists.txt.bak CMakeLists.txt
mv main/Kconfig.projbuild_bak main/Kconfig.projbuild
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
print_status "can build with phy_init_data"
idf.py clean > /dev/null
idf.py fullclean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
echo "CONFIG_ESP32_PHY_INIT_DATA_IN_PARTITION=y" >> sdkconfig.defaults
idf.py reconfigure > /dev/null
idf.py build || failure "Failed to build with PHY_INIT_DATA"
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN} ${PHY_INIT_BIN}
rm sdkconfig
rm sdkconfig.defaults
print_status "can build with ethernet component disabled"
idf.py clean > /dev/null
idf.py fullclean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
echo "CONFIG_ETH_USE_SPI_ETHERNET=" >> sdkconfig.defaults
echo "CONFIG_ETH_USE_ESP32_EMAC=" >> sdkconfig.defaults
idf.py reconfigure > /dev/null
idf.py build || failure "Failed to build with ethernet component disabled"
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN}
rm sdkconfig
rm sdkconfig.defaults
Build: CMake compiler flags will be set, regardless of the cache status Defining CMake variables from the command-line or from another CMake project, such as `-DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS=`, caused a link failure as ESP CMake was unable to set its proper compilation flags. Additional CMake compiler flags can now be provided by another project. * Closes https://github.com/espressif/esp-idf/issues/7507
2021-09-29 06:46:35 -04:00
print_status "Compiler flags on build command line are taken into account"
clean_build_dir
# Backup original source file
cp main/main.c main/main.c.bak
# Alter source file to check user flag
echo -e "\n#ifndef USER_FLAG \n \
#error \"USER_FLAG is not defined!\" \n \
#endif\n" >> main/main.c
idf.py build -DCMAKE_C_FLAGS=-DUSER_FLAG || failure "User flags should have been taken into account"
# Restore original file
mv main/main.c.bak main/main.c
print_status "Compiler flags cannot be overwritten"
clean_build_dir
# If the compiler flags are overriden, the following build command will
# cause issues at link time.
idf.py build -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= || failure "CMake compiler flags have been overriden"
idf.py: fail and show instructions on IDF_TARGET mismatch Closes IDF-869
2020-01-31 05:08:22 -05:00
# the next tests use the esp32s2 target
global: rename esp32s2beta to esp32s2
2020-01-16 22:47:08 -05:00
export other_target=esp32s2
build system: support for multiple targets
2018-10-18 23:51:51 -04:00
print_status "Can override IDF_TARGET from environment"
clean_build_dir
rm sdkconfig
ci: Use real esp32s2beta target for all tests
2019-10-31 23:44:33 -04:00
export IDF_TARGET=$other_target
build system: support for multiple targets
2018-10-18 23:51:51 -04:00
(cd build && cmake -G Ninja .. ) || failure "Failed to configure with IDF_TARGET set in environment"
ci: Use real esp32s2beta target for all tests
2019-10-31 23:44:33 -04:00
grep "CONFIG_IDF_TARGET=\"${other_target}\"" sdkconfig || failure "Project not configured for IDF_TARGET correctly"
grep "IDF_TARGET:STRING=${other_target}" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt"
build system: support for multiple targets
2018-10-18 23:51:51 -04:00
unset IDF_TARGET
print_status "Can set target using idf.py -D"
clean_build_dir
rm sdkconfig
ci: Use real esp32s2beta target for all tests
2019-10-31 23:44:33 -04:00
idf.py -DIDF_TARGET=$other_target reconfigure || failure "Failed to set target via idf.py"
grep "CONFIG_IDF_TARGET=\"${other_target}\"" sdkconfig || failure "Project not configured correctly using idf.py -D"
grep "IDF_TARGET:STRING=${other_target}" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt using idf.py -D"
build system: support for multiple targets
2018-10-18 23:51:51 -04:00
Add subcomand options that become global
2019-06-12 13:10:16 -04:00
print_status "Can set target using -D as subcommand parameter for idf.py"
clean_build_dir
rm sdkconfig
ci: Use real esp32s2beta target for all tests
2019-10-31 23:44:33 -04:00
idf.py reconfigure -DIDF_TARGET=$other_target || failure "Failed to set target via idf.py subcommand -D parameter"
grep "CONFIG_IDF_TARGET=\"${other_target}\"" sdkconfig || failure "Project not configured correctly using idf.py reconfigure -D"
grep "IDF_TARGET:STRING=${other_target}" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt using idf.py reconfigure -D"
Add subcomand options that become global
2019-06-12 13:10:16 -04:00
idf_py: support new command set-target Instead of using -DIDF_TARGET, this command is more intuitive: 1. Can limit the choice of targets 2. Easy to understand this is a destructive command 3. Easy to remember, and have an entry in the --help menu
2019-08-14 09:19:06 -04:00
print_status "Can set target using idf.py set-target"
clean_build_dir
rm sdkconfig
ci: Use real esp32s2beta target for all tests
2019-10-31 23:44:33 -04:00
idf.py set-target ${other_target} || failure "Failed to set target via idf.py set-target"
grep "CONFIG_IDF_TARGET=\"${other_target}\"" sdkconfig || failure "Project not configured correctly using idf.py set-target"
grep "IDF_TARGET:STRING=${other_target}" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt using idf.py set-target"
idf_py: support new command set-target Instead of using -DIDF_TARGET, this command is more intuitive: 1. Can limit the choice of targets 2. Easy to understand this is a destructive command 3. Easy to remember, and have an entry in the --help menu
2019-08-14 09:19:06 -04:00
tools: allow alternative spellings of target name (ESP32-S2, ESP32S2) by ignoring character case and hyphens in target name.
2020-04-03 10:21:24 -04:00
print_status "idf.py understands alternative target names"
clean_build_dir
rm sdkconfig
idf.py set-target ESP32-S2
grep "CONFIG_IDF_TARGET=\"${other_target}\"" sdkconfig || failure "Project not configured correctly using idf.py set-target"
grep "IDF_TARGET:STRING=${other_target}" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt using idf.py set-target"
idf.py: guess IDF_TARGET from sdkconfig if CMakeCache doesn't exist This solves the issue that target is changed to the default one after idf.py fullclean. Also allow setting the default target using sdkconfig.defaults, e.g. CONFIG_IDF_TARGET="esp32s2" Closes IDF-1040
2020-01-30 11:18:20 -05:00
print_status "Can guess target from sdkconfig, if CMakeCache does not exist"
idf.py fullclean || failure "Failed to clean the build directory"
idf.py reconfigure || failure "Failed to reconfigure after fullclean"
grep "CONFIG_IDF_TARGET=\"${other_target}\"" sdkconfig || failure "Didn't find the expected CONFIG_IDF_TARGET value"
grep "IDF_TARGET:STRING=${other_target}" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt after fullclean and reconfigure"
print_status "Can set the default target using sdkconfig.defaults"
clean_build_dir
rm sdkconfig
echo "CONFIG_IDF_TARGET=\"${other_target}\"" > sdkconfig.defaults
idf.py reconfigure || failure "Failed to reconfigure with default target set in sdkconfig.defaults"
grep "CONFIG_IDF_TARGET=\"${other_target}\"" sdkconfig || failure "Didn't find the expected CONFIG_IDF_TARGET value"
ci: fix build system test on macOS Replaces ${var^^} expansion supported with Bash >= 4 with 'tr'
2020-02-05 09:27:59 -05:00
other_target_caps=$(tr 'a-z' 'A-Z' <<< "${other_target}")
grep "CONFIG_IDF_TARGET_${other_target_caps}=y" sdkconfig || failure "Didn't find CONFIG_IDF_TARGET_${other_target_caps} value"
idf.py: guess IDF_TARGET from sdkconfig if CMakeCache doesn't exist This solves the issue that target is changed to the default one after idf.py fullclean. Also allow setting the default target using sdkconfig.defaults, e.g. CONFIG_IDF_TARGET="esp32s2" Closes IDF-1040
2020-01-30 11:18:20 -05:00
grep "IDF_TARGET:STRING=${other_target}" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt after fullclean and reconfigure"
rm sdkconfig.defaults
print_status "IDF_TARGET takes precedence over the value of CONFIG_IDF_TARGET in sdkconfig.defaults"
clean_build_dir
rm sdkconfig
echo "CONFIG_IDF_TARGET=\"${other_target}\"" > sdkconfig.defaults
export IDF_TARGET=esp32
idf.py reconfigure || failure "Failed to reconfigure with default target set in sdkconfig.defaults and different IDF_TARGET in the environment"
grep "CONFIG_IDF_TARGET=\"esp32\"" sdkconfig || failure "Didn't find the expected CONFIG_IDF_TARGET value"
ci: fix build system test on macOS Replaces ${var^^} expansion supported with Bash >= 4 with 'tr'
2020-02-05 09:27:59 -05:00
grep "CONFIG_IDF_TARGET_ESP32=y" sdkconfig || failure "Didn't find CONFIG_IDF_TARGET_ESP32 value"
idf.py: guess IDF_TARGET from sdkconfig if CMakeCache doesn't exist This solves the issue that target is changed to the default one after idf.py fullclean. Also allow setting the default target using sdkconfig.defaults, e.g. CONFIG_IDF_TARGET="esp32s2" Closes IDF-1040
2020-01-30 11:18:20 -05:00
grep "IDF_TARGET:STRING=esp32" build/CMakeCache.txt || failure "IDF_TARGET not set in CMakeCache.txt after fullclean and reconfigure"
rm sdkconfig.defaults
unset IDF_TARGET
idf.py: fail and show instructions on IDF_TARGET mismatch Closes IDF-869
2020-01-31 05:08:22 -05:00
print_status "idf.py fails if IDF_TARGET settings don't match in sdkconfig, CMakeCache.txt, and the environment"
clean_build_dir
rm sdkconfig
idf.py set-target ${other_target} || failure "Couldn't set target to ${other_target}"
# Change to a different IDF_TARGET in the environment
export IDF_TARGET=esp32
! idf.py reconfigure || failure "Build did't fail when IDF_TARGET was set to an incompatible value in the environment"
# Now make sdkconfig consistent with the environement (note: not really consistent, just for the purpose of the test)
echo "CONFIG_IDF_TARGET=\"esp32\"" >> sdkconfig
! idf.py reconfigure || failure "Build did't fail when IDF_TARGET in CMakeCache.txt didn't match the environment"
# Now unset IDF_TARGET in the environment, sdkconfig and CMakeCache.txt are still inconsistent
unset IDF_TARGET
! idf.py reconfigure || failure "Build did't fail when IDF_TARGET in CMakeCache.txt didn't match the sdkconfig"
ci: Use real esp32s2beta target for all tests
2019-10-31 23:44:33 -04:00
unset other_target # done changing target from the default
clean_build_dir
rm sdkconfig
build system: support for multiple targets
2018-10-18 23:51:51 -04:00
ci: add test for setting EXTRA_COMPONENT_DIRS
2018-12-04 21:44:14 -05:00
print_status "Setting EXTRA_COMPONENT_DIRS works"
clean_build_dir
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
(idf.py reconfigure | grep "$PWD/main") || failure "Failed to verify original `main` directory"
ci: add test for setting EXTRA_COMPONENT_DIRS
2018-12-04 21:44:14 -05:00
mkdir -p main/main/main # move main component contents to another directory
mv main/* main/main/main
cp CMakeLists.txt CMakeLists.bak # set EXTRA_COMPONENT_DIRS to point to the other directory
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
${SED} -i "s%cmake_minimum_required(VERSION \([0-9]\+\).\([0-9]\+\))%cmake_minimum_required(VERSION \1.\2)\nset(EXTRA_COMPONENT_DIRS main/main/main)%" CMakeLists.txt
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
(idf.py reconfigure | grep "$PWD/main/main/main") || failure "Failed to set EXTRA_COMPONENT_DIRS"
ci: add test for setting EXTRA_COMPONENT_DIRS
2018-12-04 21:44:14 -05:00
mv CMakeLists.bak CMakeLists.txt # revert previous modifications
mv main/main/main/* main
rm -rf main/main
cmake: handling of space-separated EXTRA_COMPONENT_DIRS COMPONENT_DIRS and EXTRA_COMPONENT_DIRS should be defined as CMake lists, using 'set' or 'list' commands. Some applications written for earlier versions of ESP-IDF used to define these variables as space separated strings. For example, the following is correct: set(EXTRA_COMPONENT_DIRS path/to/components path/to/more/components) The following is not correct: set(EXTRA_COMPONENT_DIRS "${EXTRA_COMPONENT_DIRS} component1") set(EXTRA_COMPONENT_DIRS "${EXTRA_COMPONENT_DIRS} component2") The string "component1 component2" may indicate a single directory name with a space, or two directory names separated by space. However due to the fact that such way of defining EXTRA_COMPONENT_DIRS was supported in IDF 4.3 and earlier, we need to provide backward compatibility for it. This commit introduces a new script, split_paths_by_spaces.py, which is invoked if EXTRA_COMPONENT_DIRS or COMPONENT_DIRS variable contains spaces. The script tries to determine if each space should be interpreted as a separator or as part of the directory name. When this cannot be done unambiguously, the script reports an error. In all cases when space separators are detected, the script reports a warning, and prints instructions for fixing the CMakeLists.txt. Breaking change in this commit: specifying non-existent directories in COMPONENT_DIRS or EXTRA_COMPONENT_DIRS is no longer allowed.
2021-10-06 03:43:05 -04:00
print_status "Non-existent paths in EXTRA_COMPONENT_DIRS are not allowed"
clean_build_dir
! idf.py -DEXTRA_COMPONENT_DIRS="extra_components" reconfigure || failure "Build should fail when non-existent component path is added"
print_status "Component names may contain spaces"
clean_build_dir
mkdir -p "extra component"
echo "idf_component_register" > "extra component/CMakeLists.txt"
idf.py -DEXTRA_COMPONENT_DIRS="extra component;main" || failure "Build should succeed when a component name contains space"
rm -rf "extra component"
ci: add tests for sdkconfig.defaults.IDF_TARGET
2019-10-29 10:12:36 -04:00
print_status "sdkconfig should have contents of all files: sdkconfig, sdkconfig.defaults, sdkconfig.defaults.IDF_TARGET"
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
idf.py clean > /dev/null
idf.py fullclean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
echo "CONFIG_PARTITION_TABLE_OFFSET=0x10000" >> sdkconfig.defaults
echo "CONFIG_ESP32_DEFAULT_CPU_FREQ_240=y" >> sdkconfig.defaults.esp32
echo "CONFIG_PARTITION_TABLE_TWO_OTA=y" >> sdkconfig
idf.py reconfigure > /dev/null
tool: Add unit test for Kconfig gen
2019-01-14 06:41:29 -05:00
grep "CONFIG_PARTITION_TABLE_OFFSET=0x10000" sdkconfig || failure "The define from sdkconfig.defaults should be into sdkconfig"
ci: add tests for sdkconfig.defaults.IDF_TARGET
2019-10-29 10:12:36 -04:00
grep "CONFIG_ESP32_DEFAULT_CPU_FREQ_240=y" sdkconfig || failure "The define from sdkconfig.defaults.esp32 should be into sdkconfig"
tool: Add unit test for Kconfig gen
2019-01-14 06:41:29 -05:00
grep "CONFIG_PARTITION_TABLE_TWO_OTA=y" sdkconfig || failure "The define from sdkconfig should be into sdkconfig"
ci: add tests for sdkconfig.defaults.IDF_TARGET
2019-10-29 10:12:36 -04:00
rm sdkconfig sdkconfig.defaults sdkconfig.defaults.esp32
tool: Add unit test for Kconfig gen
2019-01-14 06:41:29 -05:00
Add idf_as_lib/build.sh to build_system_test
2020-04-28 03:41:57 -04:00
print_status "Test if it can build the example to run on host"
pushd $IDF_PATH/examples/build_system/cmake/idf_as_lib
(set -euo pipefail && source build.sh)
popd
rm -r $IDF_PATH/examples/build_system/cmake/idf_as_lib/build
CI: idf_as_lib is now run on all suported targets
2022-01-06 02:09:48 -05:00
print_status "Test build ESP-IDF as a library to a custom CMake projects for all targets"
IDF_AS_LIB=$IDF_PATH/examples/build_system/cmake/idf_as_lib
# note: we just need to run cmake
esp8684: rename target to esp32c2
2022-01-17 21:32:56 -05:00
for TARGET in "esp32" "esp32s2" "esp32s3" "esp32c3" "esp32h2" "esp32c2"
CI: idf_as_lib is now run on all suported targets
2022-01-06 02:09:48 -05:00
do
echo "Build idf_as_lib for $TARGET target"
rm -rf build
mkdir -p build && cd build
cmake $IDF_AS_LIB -DCMAKE_TOOLCHAIN_FILE=$IDF_PATH/tools/cmake/toolchain-$TARGET.cmake -DTARGET=$TARGET || failure "Failed to generate idf_as_lib build files for target $TARGET"
cmake --build . || failure "Failed to build idf_as_lib for target $TARGET"
cd ..
done
cmake: Fix psram workaround compiler flag application Previously, this compiler flag was not being applied regardless of CONFIG_SPIRAM_CACHE_WORKAROUND setting. Explanation: add_compile_options() only applies to source files added after the function is run, or in subdirectories added after the function is run. In this case, no new source files were being added after this function was run.
2019-02-21 20:20:11 -05:00
print_status "Building a project with CMake library imported and PSRAM workaround, all files compile with workaround"
examples: update idf_as_lib example to use new api
2019-03-23 22:14:49 -04:00
# Test for libraries compiled within ESP-IDF
examples: Move idf_as_lib sdkconfig file to the project directory Also add some explanation about configuring the project in the README Previously with the default build-esp32.sh script, the build directory was deleted and recreated so the project would always be built with default config.
2020-05-07 20:39:39 -04:00
rm -r build sdkconfig
Rename Kconfig options (components/esp32)
2019-04-30 06:51:55 -04:00
echo "CONFIG_ESP32_SPIRAM_SUPPORT=y" >> sdkconfig.defaults
ci: test full build never runs '/usr/bin/env python' or similar
2019-03-12 01:28:06 -04:00
echo "CONFIG_SPIRAM_CACHE_WORKAROUND=y" >> sdkconfig.defaults
cmake: Fix psram workaround compiler flag application Previously, this compiler flag was not being applied regardless of CONFIG_SPIRAM_CACHE_WORKAROUND setting. Explanation: add_compile_options() only applies to source files added after the function is run, or in subdirectories added after the function is run. In this case, no new source files were being added after this function was run.
2019-02-21 20:20:11 -05:00
# note: we do 'reconfigure' here, as we just need to run cmake
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 12:06:52 -04:00
idf.py -C $IDF_PATH/examples/build_system/cmake/import_lib -B `pwd`/build -D SDKCONFIG_DEFAULTS="`pwd`/sdkconfig.defaults" reconfigure
cmake: Fix psram workaround compiler flag application Previously, this compiler flag was not being applied regardless of CONFIG_SPIRAM_CACHE_WORKAROUND setting. Explanation: add_compile_options() only applies to source files added after the function is run, or in subdirectories added after the function is run. In this case, no new source files were being added after this function was run.
2019-02-21 20:20:11 -05:00
grep -q '"command"' build/compile_commands.json || failure "compile_commands.json missing or has no no 'commands' in it"
(grep '"command"' build/compile_commands.json | grep -v mfix-esp32-psram-cache-issue) && failure "All commands in compile_commands.json should use PSRAM cache workaround"
examples: Move idf_as_lib sdkconfig file to the project directory Also add some explanation about configuring the project in the README Previously with the default build-esp32.sh script, the build directory was deleted and recreated so the project would always be built with default config.
2020-05-07 20:39:39 -04:00
rm -r build sdkconfig sdkconfig.defaults
print_status "Test for external libraries in custom CMake projects with ESP-IDF components linked"
mkdir build
IDF_AS_LIB=$IDF_PATH/examples/build_system/cmake/idf_as_lib
echo "CONFIG_ESP32_SPIRAM_SUPPORT=y" > $IDF_AS_LIB/sdkconfig
echo "CONFIG_SPIRAM_CACHE_WORKAROUND=y" >> $IDF_AS_LIB/sdkconfig
examples: update idf_as_lib example to use new api
2019-03-23 22:14:49 -04:00
# note: we just need to run cmake
examples: Move idf_as_lib sdkconfig file to the project directory Also add some explanation about configuring the project in the README Previously with the default build-esp32.sh script, the build directory was deleted and recreated so the project would always be built with default config.
2020-05-07 20:39:39 -04:00
(cd build && cmake $IDF_AS_LIB -DCMAKE_TOOLCHAIN_FILE=$IDF_PATH/tools/cmake/toolchain-esp32.cmake -DTARGET=esp32)
examples: update idf_as_lib example to use new api
2019-03-23 22:14:49 -04:00
grep -q '"command"' build/compile_commands.json || failure "compile_commands.json missing or has no no 'commands' in it"
(grep '"command"' build/compile_commands.json | grep -v mfix-esp32-psram-cache-issue) && failure "All commands in compile_commands.json should use PSRAM cache workaround"
examples: Move idf_as_lib sdkconfig file to the project directory Also add some explanation about configuring the project in the README Previously with the default build-esp32.sh script, the build directory was deleted and recreated so the project would always be built with default config.
2020-05-07 20:39:39 -04:00
Add fixes for gcc8 psram fix improvement
2019-12-18 01:36:58 -05:00
for strat in MEMW NOPS DUPLDST; do
examples: Move idf_as_lib sdkconfig file to the project directory Also add some explanation about configuring the project in the README Previously with the default build-esp32.sh script, the build directory was deleted and recreated so the project would always be built with default config.
2020-05-07 20:39:39 -04:00
print_status "Test for external libraries in custom CMake projects with PSRAM strategy $strat"
rm -r build sdkconfig sdkconfig.defaults sdkconfig.defaults.esp32
Add fixes for gcc8 psram fix improvement
2019-12-18 01:36:58 -05:00
stratlc=`echo $strat | tr A-Z a-z`
echo "CONFIG_ESP32_SPIRAM_SUPPORT=y" > sdkconfig.defaults
echo "CONFIG_SPIRAM_CACHE_WORKAROUND_STRATEGY_$strat=y" >> sdkconfig.defaults
echo "CONFIG_SPIRAM_CACHE_WORKAROUND=y" >> sdkconfig.defaults
# note: we do 'reconfigure' here, as we just need to run cmake
idf.py reconfigure
grep -q '"command"' build/compile_commands.json || failure "compile_commands.json missing or has no no 'commands' in it"
examples: Move idf_as_lib sdkconfig file to the project directory Also add some explanation about configuring the project in the README Previously with the default build-esp32.sh script, the build directory was deleted and recreated so the project would always be built with default config.
2020-05-07 20:39:39 -04:00
(grep '"command"' build/compile_commands.json | grep -v mfix-esp32-psram-cache-strategy=$stratlc) && failure "All commands in compile_commands.json should use PSRAM cache workaround strategy"
Add fixes for gcc8 psram fix improvement
2019-12-18 01:36:58 -05:00
echo ${PWD}
rm -r sdkconfig.defaults build
done
ci: test full build never runs '/usr/bin/env python' or similar
2019-03-12 01:28:06 -04:00
tools/idf.py: Clean Python bytecode files
2020-05-25 08:17:07 -04:00
print_status "Cleaning Python bytecode"
idf.py clean > /dev/null
idf.py fullclean > /dev/null
if [ "$(find $IDF_PATH -name "*.py[co]" | wc -l)" -eq 0 ]; then
failure "No Python bytecode in IDF!"
fi
idf.py python-clean
if [ "$(find $IDF_PATH -name "*.py[co]" | wc -l)" -gt 0 ]; then
failure "Python bytecode isn't working!"
fi
ci: add test for partition_table target
2020-03-04 22:04:01 -05:00
print_status "Displays partition table when executing target partition_table"
tools: replace _ with - in idf.py Closes https://github.com/espressif/esp-idf/issues/5126
2021-08-11 09:24:17 -04:00
idf.py partition-table | grep -E "# ESP-IDF .+ Partition Table"
ci: add test for partition_table target
2020-03-04 22:04:01 -05:00
rm -r build
ci: test full build never runs '/usr/bin/env python' or similar
2019-03-12 01:28:06 -04:00
print_status "Make sure a full build never runs '/usr/bin/env python' or similar"
OLDPATH="$PATH"
PYTHON="$(which python)"
rm -rf build
cat > ./python << EOF
#!/bin/sh
echo "The build system has executed '/usr/bin/env python' or similar"
exit 1
EOF
chmod +x ./python
export PATH="$(pwd):$PATH"
${PYTHON} $IDF_PATH/tools/idf.py build || failure "build failed"
export PATH="$OLDPATH"
rm ./python
cmake: Fix psram workaround compiler flag application Previously, this compiler flag was not being applied regardless of CONFIG_SPIRAM_CACHE_WORKAROUND setting. Explanation: add_compile_options() only applies to source files added after the function is run, or in subdirectories added after the function is run. In this case, no new source files were being added after this function was run.
2019-02-21 20:20:11 -05:00
Rename deprecated Kconfig options in a backward compatible way
2019-03-14 04:54:04 -04:00
print_status "Handling deprecated Kconfig options"
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
idf.py clean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
echo "" > ${IDF_PATH}/sdkconfig.rename
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
idf.py reconfigure > /dev/null
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
echo "CONFIG_TEST_OLD_OPTION=y" >> sdkconfig
echo "CONFIG_TEST_OLD_OPTION CONFIG_TEST_NEW_OPTION" >> ${IDF_PATH}/sdkconfig.rename
Rename deprecated Kconfig options in a backward compatible way
2019-03-14 04:54:04 -04:00
echo -e "\n\
menu \"test\"\n\
config TEST_NEW_OPTION\n\
bool \"test\"\n\
default \"n\"\n\
help\n\
TEST_NEW_OPTION description\n\
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
endmenu\n" >> ${IDF_PATH}/Kconfig
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
idf.py reconfigure > /dev/null
Rename deprecated Kconfig options in a backward compatible way
2019-03-14 04:54:04 -04:00
grep "CONFIG_TEST_OLD_OPTION=y" sdkconfig || failure "CONFIG_TEST_OLD_OPTION should be in sdkconfig for backward compatibility"
grep "CONFIG_TEST_NEW_OPTION=y" sdkconfig || failure "CONFIG_TEST_NEW_OPTION should be now in sdkconfig"
grep "#define CONFIG_TEST_NEW_OPTION 1" build/config/sdkconfig.h || failure "sdkconfig.h should contain the new macro"
grep "#define CONFIG_TEST_OLD_OPTION CONFIG_TEST_NEW_OPTION" build/config/sdkconfig.h || failure "sdkconfig.h should contain the compatibility macro"
grep "set(CONFIG_TEST_OLD_OPTION \"y\")" build/config/sdkconfig.cmake || failure "CONFIG_TEST_OLD_OPTION should be in auto.conf for backward compatibility"
grep "set(CONFIG_TEST_NEW_OPTION \"y\")" build/config/sdkconfig.cmake || failure "CONFIG_TEST_NEW_OPTION should be now in auto.conf"
rm -f sdkconfig sdkconfig.defaults
pushd ${IDF_PATH}
git checkout -- sdkconfig.rename Kconfig
popd
ci: check that build uses ccache when present
2019-05-06 07:58:06 -04:00
Handle deprecated values in sdkconfig.defaults The issue was pointed out also in https://github.com/espressif/esp-idf/issues/4092
2019-09-25 09:58:02 -04:00
print_status "Handling deprecated Kconfig options in sdkconfig.defaults"
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
idf.py clean
rm -f sdkconfig
echo "CONFIG_TEST_OLD_OPTION=7" > sdkconfig.defaults
echo "CONFIG_TEST_OLD_OPTION CONFIG_TEST_NEW_OPTION" > ${IDF_PATH}/sdkconfig.rename
Handle deprecated values in sdkconfig.defaults The issue was pointed out also in https://github.com/espressif/esp-idf/issues/4092
2019-09-25 09:58:02 -04:00
echo -e "\n\
menu \"test\"\n\
config TEST_NEW_OPTION\n\
int \"TEST_NEW_OPTION\"\n\
range 0 10\n\
default 5\n\
help\n\
TEST_NEW_OPTION description\n\
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
endmenu\n" >> ${IDF_PATH}/Kconfig
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
idf.py reconfigure > /dev/null
Handle deprecated values in sdkconfig.defaults The issue was pointed out also in https://github.com/espressif/esp-idf/issues/4092
2019-09-25 09:58:02 -04:00
grep "CONFIG_TEST_OLD_OPTION=7" sdkconfig || failure "CONFIG_TEST_OLD_OPTION=7 should be in sdkconfig for backward compatibility"
grep "CONFIG_TEST_NEW_OPTION=7" sdkconfig || failure "CONFIG_TEST_NEW_OPTION=7 should be in sdkconfig"
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
rm -f sdkconfig.defaults
Handle deprecated values in sdkconfig.defaults The issue was pointed out also in https://github.com/espressif/esp-idf/issues/4092
2019-09-25 09:58:02 -04:00
pushd ${IDF_PATH}
git checkout -- sdkconfig.rename Kconfig
popd
kconfig: confgen.py now handles many-to-one config renames All old symbols will now be included in the output when renaming multiple symbols to the same new symbol.
2022-01-30 21:56:14 -05:00
echo "Can have multiple deprecated Kconfig options map to a single new option"
idf.py clean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
echo "" > ${IDF_PATH}/sdkconfig.rename
idf.py reconfigure > /dev/null
echo "CONFIG_TEST_NEW_OPTION=y" >> sdkconfig
echo "CONFIG_TEST_OLD_OPTION_1 CONFIG_TEST_NEW_OPTION" >> ${IDF_PATH}/sdkconfig.rename
echo "CONFIG_TEST_OLD_OPTION_2 CONFIG_TEST_NEW_OPTION" >> ${IDF_PATH}/sdkconfig.rename
echo -e "\n\
menu \"test\"\n\
config TEST_NEW_OPTION\n\
bool \"test\"\n\
default \"n\"\n\
help\n\
TEST_NEW_OPTION description\n\
endmenu\n" >> ${IDF_PATH}/Kconfig
idf.py reconfigure > /dev/null
grep "CONFIG_TEST_OLD_OPTION_1=y" sdkconfig || failure "CONFIG_TEST_OLD_OPTION_1 should be in sdkconfig for backward compatibility"
grep "CONFIG_TEST_OLD_OPTION_2=y" sdkconfig || failure "CONFIG_TEST_OLD_OPTION_2 should be in sdkconfig for backward compatibility"
grep "#define CONFIG_TEST_OLD_OPTION_1 CONFIG_TEST_NEW_OPTION" build/config/sdkconfig.h || failure "sdkconfig.h should contain the compatibility macro"
grep "#define CONFIG_TEST_OLD_OPTION_2 CONFIG_TEST_NEW_OPTION" build/config/sdkconfig.h || failure "sdkconfig.h should contain the compatibility macro"
grep "set(CONFIG_TEST_OLD_OPTION_1 \"y\")" build/config/sdkconfig.cmake || failure "CONFIG_TEST_OLD_OPTION_1 should be in auto.conf for backward compatibility"
grep "set(CONFIG_TEST_OLD_OPTION_2 \"y\")" build/config/sdkconfig.cmake || failure "CONFIG_TEST_OLD_OPTION_2 should be in auto.conf for backward compatibility"
rm -rf sdkconfig sdkconfig.defaults build
pushd ${IDF_PATH}
git checkout -- sdkconfig.rename Kconfig
popd
kconfig: also parse target specific sdkconfig.rename.TARGET files Adds functionality for target specific sdkconfig.rename files which can be used when certain renames are only needed for a specific target.
2022-01-30 21:53:59 -05:00
echo "Can have target specific deprecated Kconfig options"
idf.py clean
rm -f sdkconfig
echo "CONFIG_TEST_OLD_OPTION=y" > sdkconfig
echo "CONFIG_TEST_OLD_OPTION CONFIG_TEST_NEW_OPTION" >> ${IDF_PATH}/components/esp_system/sdkconfig.rename.esp32s2
echo -e "\n\
menu \"test\"\n\
config TEST_NEW_OPTION\n\
bool \"TEST_NEW_OPTION\"\n\
default y\n\
help\n\
TEST_NEW_OPTION description\n\
endmenu\n" >> ${IDF_PATH}/Kconfig
idf.py set-target esp32 > /dev/null
grep "CONFIG_TEST_OLD_OPTION=y" sdkconfig && failure "CONFIG_TEST_OLD_OPTION=y should NOT be in sdkconfig"
grep "CONFIG_TEST_NEW_OPTION=y" sdkconfig || failure "CONFIG_TEST_NEW_OPTION=y should be in sdkconfig"
rm -f sdkconfig
idf.py set-target esp32s2 > /dev/null
grep "CONFIG_TEST_OLD_OPTION=y" sdkconfig || failure "CONFIG_TEST_OLD_OPTION=y should be in esp32s2's sdkconfig for backward compatibility"
grep "CONFIG_TEST_NEW_OPTION=y" sdkconfig || failure "CONFIG_TEST_NEW_OPTION=y should be in sdkconfig"
rm -rf sdkconfig sdkconfig.defaults build
pushd ${IDF_PATH}
git checkout -- components/esp_system/sdkconfig.rename.esp32s2 Kconfig
popd
Fix cmake confserver target
2019-05-22 04:04:25 -04:00
print_status "Confserver can be invoked by idf.py"
echo '{"version": 1}' | idf.py confserver || failure "Couldn't load confserver"
cmake: make use of ccache opt-in
2019-06-27 02:25:28 -04:00
print_status "Check ccache is used to build"
ci: check that build uses ccache when present
2019-05-06 07:58:06 -04:00
touch ccache && chmod +x ccache # make sure that ccache is present for this test
idf.py: Add environment variable to enable ccache by default
2019-09-01 20:56:56 -04:00
(export PATH=$PWD:$PATH && idf.py --ccache reconfigure | grep "ccache will be used") || failure "ccache should be used when --cache is specified"
cmake: make use of ccache opt-in
2019-06-27 02:25:28 -04:00
idf.py fullclean
idf.py: Add environment variable to enable ccache by default
2019-09-01 20:56:56 -04:00
(export PATH=$PWD:$PATH && idf.py reconfigure| grep -c "ccache will be used" | grep -wq 0) \
cmake: make use of ccache opt-in
2019-06-27 02:25:28 -04:00
|| failure "ccache should not be used even when present if --ccache is not specified"
idf.py: Add environment variable to enable ccache by default
2019-09-01 20:56:56 -04:00
(export PATH=$PWD:$PATH && idf.py --no-ccache reconfigure| grep -c "ccache will be used" | grep -wq 0) \
cmake: make use of ccache opt-in
2019-06-27 02:25:28 -04:00
|| failure "--no-ccache causes no issue for backward compatibility"
ci: check that build uses ccache when present
2019-05-06 07:58:06 -04:00
rm -f ccache
Rename deprecated Kconfig options in a backward compatible way
2019-03-14 04:54:04 -04:00
ci: check that custom bootloader overrides original
2019-05-15 02:49:51 -04:00
print_status "Custom bootloader overrides original"
clean_build_dir
(mkdir components && cd components && cp -r $IDF_PATH/components/bootloader .)
cmake: some optimizations to build system tests
2019-12-10 06:17:34 -05:00
idf.py bootloader
ci: check that custom bootloader overrides original
2019-05-15 02:49:51 -04:00
grep "$PWD/components/bootloader/subproject/main/bootloader_start.c" build/bootloader/compile_commands.json \
|| failure "Custom bootloader source files should be built instead of the original's"
rm -rf components
ci: additional Cmake tests for EXTRA_COMPONENT_DIRS Tests from https://gitlab.espressif.cn:6688/idf/esp-idf/merge_requests/4253
2019-05-30 06:23:00 -04:00
print_status "Empty directory not treated as a component"
clean_build_dir
mkdir -p components/esp32 && idf.py reconfigure
! grep "$PWD/components/esp32" $PWD/build/project_description.json || failure "Failed to build with empty esp32 directory in components"
rm -rf components
print_status "If a component directory is added to COMPONENT_DIRS, its subdirectories are not added"
clean_build_dir
mkdir -p main/test
echo "idf_component_register()" > main/test/CMakeLists.txt
idf.py reconfigure
! grep "$PWD/main/test" $PWD/build/project_description.json || failure "COMPONENT_DIRS has added component subdirectory to the build"
grep "$PWD/main" $PWD/build/project_description.json || failure "COMPONENT_DIRS parent component directory should be included in the build"
rm -rf main/test
print_status "If a component directory is added to COMPONENT_DIRS, its sibling directories are not added"
clean_build_dir
esp_wifi: fix wrong path of phy_init_data Closes https://github.com/espressif/esp-idf/issues/3482
2019-06-11 23:52:23 -04:00
mkdir -p mycomponents/mycomponent
ci: additional Cmake tests for EXTRA_COMPONENT_DIRS Tests from https://gitlab.espressif.cn:6688/idf/esp-idf/merge_requests/4253
2019-05-30 06:23:00 -04:00
echo "idf_component_register()" > mycomponents/mycomponent/CMakeLists.txt
# first test by adding single component directory to EXTRA_COMPONENT_DIRS
mkdir -p mycomponents/esp32
echo "idf_component_register()" > mycomponents/esp32/CMakeLists.txt
ci: fix idf.py syntax in new build system tests
2019-06-07 10:03:15 -04:00
idf.py -DEXTRA_COMPONENT_DIRS=$PWD/mycomponents/mycomponent reconfigure
ci: additional Cmake tests for EXTRA_COMPONENT_DIRS Tests from https://gitlab.espressif.cn:6688/idf/esp-idf/merge_requests/4253
2019-05-30 06:23:00 -04:00
! grep "$PWD/mycomponents/esp32" $PWD/build/project_description.json || failure "EXTRA_COMPONENT_DIRS has added a sibling directory"
grep "$PWD/mycomponents/mycomponent" $PWD/build/project_description.json || failure "EXTRA_COMPONENT_DIRS valid sibling directory should be in the build"
rm -rf mycomponents/esp32
# now the same thing, but add a components directory
mkdir -p esp32
echo "idf_component_register()" > esp32/CMakeLists.txt
ci: fix idf.py syntax in new build system tests
2019-06-07 10:03:15 -04:00
idf.py -DEXTRA_COMPONENT_DIRS=$PWD/mycomponents reconfigure
ci: additional Cmake tests for EXTRA_COMPONENT_DIRS Tests from https://gitlab.espressif.cn:6688/idf/esp-idf/merge_requests/4253
2019-05-30 06:23:00 -04:00
! grep "$PWD/esp32" $PWD/build/project_description.json || failure "EXTRA_COMPONENT_DIRS has added a sibling directory"
grep "$PWD/mycomponents/mycomponent" $PWD/build/project_description.json || failure "EXTRA_COMPONENT_DIRS valid sibling directory should be in the build"
rm -rf esp32
rm -rf mycomponents
cmake: assign toolchain prefix manually
2022-01-20 02:45:13 -05:00
print_status "toolchain prefix is set in project description file"
clean_build_dir
idf.py reconfigure
grep "prefix.*esp.*elf-" $PWD/build/project_description.json || failure "toolchain prefix not set or determined by CMake"
idf.py: Fix subcommand options
2019-06-27 14:23:14 -04:00
# idf.py subcommand options, (using monitor with as example)
print_status "Can set options to subcommands: print_filter for monitor"
cmake: handling of space-separated EXTRA_COMPONENT_DIRS COMPONENT_DIRS and EXTRA_COMPONENT_DIRS should be defined as CMake lists, using 'set' or 'list' commands. Some applications written for earlier versions of ESP-IDF used to define these variables as space separated strings. For example, the following is correct: set(EXTRA_COMPONENT_DIRS path/to/components path/to/more/components) The following is not correct: set(EXTRA_COMPONENT_DIRS "${EXTRA_COMPONENT_DIRS} component1") set(EXTRA_COMPONENT_DIRS "${EXTRA_COMPONENT_DIRS} component2") The string "component1 component2" may indicate a single directory name with a space, or two directory names separated by space. However due to the fact that such way of defining EXTRA_COMPONENT_DIRS was supported in IDF 4.3 and earlier, we need to provide backward compatibility for it. This commit introduces a new script, split_paths_by_spaces.py, which is invoked if EXTRA_COMPONENT_DIRS or COMPONENT_DIRS variable contains spaces. The script tries to determine if each space should be interpreted as a separator or as part of the directory name. When this cannot be done unambiguously, the script reports an error. In all cases when space separators are detected, the script reports a warning, and prints instructions for fixing the CMakeLists.txt. Breaking change in this commit: specifying non-existent directories in COMPONENT_DIRS or EXTRA_COMPONENT_DIRS is no longer allowed.
2021-10-06 03:43:05 -04:00
clean_build_dir
idf.py: Fix subcommand options
2019-06-27 14:23:14 -04:00
mv ${IDF_PATH}/tools/idf_monitor.py ${IDF_PATH}/tools/idf_monitor.py.tmp
echo "import sys;print(sys.argv[1:])" > ${IDF_PATH}/tools/idf_monitor.py
cmake: handling of space-separated EXTRA_COMPONENT_DIRS COMPONENT_DIRS and EXTRA_COMPONENT_DIRS should be defined as CMake lists, using 'set' or 'list' commands. Some applications written for earlier versions of ESP-IDF used to define these variables as space separated strings. For example, the following is correct: set(EXTRA_COMPONENT_DIRS path/to/components path/to/more/components) The following is not correct: set(EXTRA_COMPONENT_DIRS "${EXTRA_COMPONENT_DIRS} component1") set(EXTRA_COMPONENT_DIRS "${EXTRA_COMPONENT_DIRS} component2") The string "component1 component2" may indicate a single directory name with a space, or two directory names separated by space. However due to the fact that such way of defining EXTRA_COMPONENT_DIRS was supported in IDF 4.3 and earlier, we need to provide backward compatibility for it. This commit introduces a new script, split_paths_by_spaces.py, which is invoked if EXTRA_COMPONENT_DIRS or COMPONENT_DIRS variable contains spaces. The script tries to determine if each space should be interpreted as a separator or as part of the directory name. When this cannot be done unambiguously, the script reports an error. In all cases when space separators are detected, the script reports a warning, and prints instructions for fixing the CMakeLists.txt. Breaking change in this commit: specifying non-existent directories in COMPONENT_DIRS or EXTRA_COMPONENT_DIRS is no longer allowed.
2021-10-06 03:43:05 -04:00
idf.py build || failure "Failed to build project"
idf.py: Fix subcommand options
2019-06-27 14:23:14 -04:00
idf.py monitor --print-filter="*:I" -p tty.fake | grep "'--print_filter', '\*:I'" || failure "It should process options for subcommands (and pass print-filter to idf_monitor.py)"
mv ${IDF_PATH}/tools/idf_monitor.py.tmp ${IDF_PATH}/tools/idf_monitor.py
ci: test fail on build time works
2019-05-29 23:50:39 -04:00
print_status "Fail on build time works"
clean_build_dir
cp CMakeLists.txt CMakeLists.txt.bak
printf "\nif(NOT EXISTS \"\${CMAKE_CURRENT_LIST_DIR}/hello.txt\") \nfail_at_build_time(test_file \"hello.txt does not exists\") \nendif()" >> CMakeLists.txt
! idf.py build || failure "Build should fail if requirements are not satisfied"
touch hello.txt
idf.py build || failure "Build succeeds once requirements are satisfied"
rm -rf hello.txt CMakeLists.txt
mv CMakeLists.txt.bak CMakeLists.txt
rm -rf CMakeLists.txt.bak
cmake: set component properties
2019-08-09 00:30:23 -04:00
print_status "Component properties are set"
clean_build_dir
cp CMakeLists.txt CMakeLists.txt.bak
printf "\nidf_component_get_property(srcs main SRCS)\nmessage(STATUS SRCS:\${srcs})" >> CMakeLists.txt
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
(idf.py reconfigure | grep "SRCS:$(${REALPATH} main/main.c)") || failure "Component properties should be set"
cmake: set component properties
2019-08-09 00:30:23 -04:00
rm -rf CMakeLists.txt
mv CMakeLists.txt.bak CMakeLists.txt
rm -rf CMakeLists.txt.bak
ethernet: test apps can build with ethernet disabled
2019-09-18 06:28:18 -04:00
ci: test multiple sdkconfig defaults
2019-10-22 03:34:17 -04:00
print_status "should be able to specify multiple sdkconfig default files"
ci: remove semicolon for cmake build system test
2019-10-30 01:30:51 -04:00
idf.py clean > /dev/null
idf.py fullclean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
echo "CONFIG_PARTITION_TABLE_OFFSET=0x10000" >> sdkconfig.defaults1
echo "CONFIG_PARTITION_TABLE_TWO_OTA=y" >> sdkconfig.defaults2
idf.py -DSDKCONFIG_DEFAULTS="sdkconfig.defaults1;sdkconfig.defaults2" reconfigure > /dev/null
ci: test multiple sdkconfig defaults
2019-10-22 03:34:17 -04:00
grep "CONFIG_PARTITION_TABLE_OFFSET=0x10000" sdkconfig || failure "The define from sdkconfig.defaults1 should be in sdkconfig"
grep "CONFIG_PARTITION_TABLE_TWO_OTA=y" sdkconfig || failure "The define from sdkconfig.defaults2 should be in sdkconfig"
Use component manager if available as python package
2019-11-18 11:34:33 -05:00
rm sdkconfig.defaults1 sdkconfig.defaults2 sdkconfig
git checkout sdkconfig.defaults
ci: test multiple sdkconfig defaults
2019-10-22 03:34:17 -04:00
cmake: support git worktree Use rev-parse to get the HEAD directory instead of manually looking for it. This method works in the main repository, worktrees and submodules. Closes https://github.com/espressif/esp-idf/issues/4136
2019-11-04 07:19:13 -05:00
print_status "Supports git worktree"
clean_build_dir
git branch test_build_system
git worktree add ../esp-idf-template-test test_build_system
build: Add CONFIG_APP_PROJECT_VER to set the project version from Kconfig
2019-11-27 06:01:40 -05:00
diff <(idf.py reconfigure | grep "App \"app-template\" version: ") <(cd ../esp-idf-template-test && idf.py reconfigure | grep "App \"app-template\" version: ") \
cmake: support git worktree Use rev-parse to get the HEAD directory instead of manually looking for it. This method works in the main repository, worktrees and submodules. Closes https://github.com/espressif/esp-idf/issues/4136
2019-11-04 07:19:13 -05:00
|| failure "Version on worktree should have been properly resolved"
git worktree remove ../esp-idf-template-test
idf.py: fix fallback to build system target
2019-11-28 08:47:41 -05:00
print_status "idf.py fallback to build system target"
clean_build_dir
msg="Custom target is running"
echo "" >> CMakeLists.txt
echo "add_custom_target(custom_target COMMAND \${CMAKE_COMMAND} -E echo \"${msg}\")" >> CMakeLists.txt
idf.py custom_target 1>log.txt || failure "Could not invoke idf.py with custom target"
grep "${msg}" log.txt 1>/dev/null || failure "Custom target did not produce expected output"
git checkout CMakeLists.txt
rm -f log.txt
ci: add build system tests for bootloader flash mode/freq/size
2020-01-23 06:20:22 -05:00
print_status "Build fails if partitions don't fit in flash"
ci: Fix build system tests to clean the dir
2021-11-26 00:23:14 -05:00
clean_build_dir
ci: add build system tests for bootloader flash mode/freq/size
2020-01-23 06:20:22 -05:00
sed -i.bak "s/CONFIG_ESPTOOLPY_FLASHSIZE.\+//" sdkconfig # remove all flashsize config
echo "CONFIG_ESPTOOLPY_FLASHSIZE_1MB=y" >> sdkconfig # introduce undersize flash
( idf.py build 2>&1 | grep "does not fit in configured flash size 1MB" ) || failure "Build didn't fail with expected flash size failure message"
mv sdkconfig.bak sdkconfig
print_status "Flash size is correctly set in the bootloader image header"
# Build with the default 2MB setting
rm sdkconfig
idf.py bootloader || failure "Failed to build bootloader"
bin_header_match build/bootloader/bootloader.bin "0210"
# Change to 4MB
ci: test_build_system_cmake: ensure sdkconfig timestamp changes idf.py bootloader runs very quickly on some build servers, so when sdkconfig is modified, the next idf.py invocation doesn't pick up the timestamp difference. Add some delays to make sure the change is noticed.
2020-02-07 03:35:41 -05:00
sleep 1 # delay here to make sure sdkconfig modification time is different
ci: add build system tests for bootloader flash mode/freq/size
2020-01-23 06:20:22 -05:00
echo "CONFIG_ESPTOOLPY_FLASHSIZE_4MB=y" > sdkconfig
idf.py bootloader || failure "Failed to build bootloader"
bin_header_match build/bootloader/bootloader.bin "0220"
# Change to QIO, bootloader should still be DIO (will change to QIO in 2nd stage bootloader)
ci: test_build_system_cmake: ensure sdkconfig timestamp changes idf.py bootloader runs very quickly on some build servers, so when sdkconfig is modified, the next idf.py invocation doesn't pick up the timestamp difference. Add some delays to make sure the change is noticed.
2020-02-07 03:35:41 -05:00
sleep 1 # delay here to make sure sdkconfig modification time is different
ci: add build system tests for bootloader flash mode/freq/size
2020-01-23 06:20:22 -05:00
echo "CONFIG_FLASHMODE_QIO=y" > sdkconfig
idf.py bootloader || failure "Failed to build bootloader"
bin_header_match build/bootloader/bootloader.bin "0210"
# Change to 80 MHz
ci: test_build_system_cmake: ensure sdkconfig timestamp changes idf.py bootloader runs very quickly on some build servers, so when sdkconfig is modified, the next idf.py invocation doesn't pick up the timestamp difference. Add some delays to make sure the change is noticed.
2020-02-07 03:35:41 -05:00
sleep 1 # delay here to make sure sdkconfig modification time is different
ci: add build system tests for bootloader flash mode/freq/size
2020-01-23 06:20:22 -05:00
echo "CONFIG_ESPTOOLPY_FLASHFREQ_80M=y" > sdkconfig
idf.py bootloader || failure "Failed to build bootloader"
bin_header_match build/bootloader/bootloader.bin "021f"
rm sdkconfig
Add build system support for programming ESP32-S2 using DFU utils
2020-04-06 10:41:44 -04:00
print_status "DFU build works"
rm -f -r build sdkconfig
idf.py dfu &> tmp.log
grep "command \"dfu\" is not known to idf.py and is not a Ninja target" tmp.log || (tail -n 100 tmp.log ; failure "DFU build should fail for default chip target")
idf.py set-target esp32s2
idf.py dfu &> tmp.log
grep "build/dfu.bin\" has been written. You may proceed with DFU flashing." tmp.log || (tail -n 100 tmp.log ; failure "DFU build should succeed for esp32s2")
rm tmp.log
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN} "dfu.bin"
ci: add loadable ELF build system test
2020-05-04 13:15:43 -04:00
rm -rf build sdkconfig
tools: Wrap flash binaries into a UF2 file for flashing through USB MSC @mmoskal This commit adds basic support for UF2 into ESP-IDF.
2020-12-11 10:28:11 -05:00
print_status "UF2 build works"
rm -f -r build sdkconfig
idf.py uf2 &> tmp.log
grep "build/uf2.bin\" has been written." tmp.log || (tail -n 100 tmp.log ; failure "UF2 build works for esp32")
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN} "uf2.bin"
idf.py uf2-app &> tmp.log
grep "build/uf2-app.bin\" has been written." tmp.log || (tail -n 100 tmp.log ; failure "UF2 build works for application binary")
assert_built "uf2-app.bin"
idf.py set-target esp32s2
idf.py uf2 &> tmp.log
grep "build/uf2.bin\" has been written." tmp.log || (tail -n 100 tmp.log ; failure "UF2 build works for esp32s2")
rm tmp.log
assert_built ${APP_BINS} ${BOOTLOADER_BINS} ${PARTITION_BIN} "uf2.bin"
rm -rf build sdkconfig
ci: add loadable ELF build system test
2020-05-04 13:15:43 -04:00
print_status "Loadable ELF build works"
echo "CONFIG_APP_BUILD_TYPE_ELF_RAM=y" > sdkconfig
idf.py reconfigure || failure "Couldn't configure for loadable ELF file"
test -f build/flasher_args.json && failure "flasher_args.json should not be generated in a loadable ELF build"
idf.py build || failure "Couldn't build a loadable ELF file"
Add build system support for programming ESP32-S2 using DFU utils
2020-04-06 10:41:44 -04:00
ci: test idf_build_process defaults set properly
2020-05-04 08:56:40 -04:00
print_status "Defaults set properly for unspecified idf_build_process args"
ci: pushd and cd in one go in idf_build_process defaults test
2020-05-14 04:26:52 -04:00
pushd $IDF_PATH/examples/build_system/cmake/idf_as_lib
ci: test idf_build_process defaults set properly
2020-05-04 08:56:40 -04:00
cp CMakeLists.txt CMakeLists.txt.bak
echo -e "\nidf_build_get_property(project_dir PROJECT_DIR)" >> CMakeLists.txt
echo -e "\nmessage(\"Project directory: \${project_dir}\")" >> CMakeLists.txt
mkdir build && cd build
cmake .. -DCMAKE_TOOLCHAIN_FILE=$IDF_PATH/tools/cmake/toolchain-esp32.cmake -DTARGET=esp32 &> log.txt
grep "Project directory: $IDF_PATH/examples/build_system/cmake/idf_as_lib" log.txt || failure "PROJECT_DIR default was not set"
cd ..
mv CMakeLists.txt.bak CMakeLists.txt
rm -rf build
popd
ci: add test for component override features
2020-04-02 10:33:48 -04:00
print_status "Getting component overriden dir"
clean_build_dir
mkdir -p components/esp32
echo "idf_component_get_property(overriden_dir \${COMPONENT_NAME} COMPONENT_OVERRIDEN_DIR)" >> components/esp32/CMakeLists.txt
add new command to idf
2020-09-03 05:16:42 -04:00
echo "message(STATUS overriden_dir:\${overriden_dir})" >> components/esp32/CMakeLists.txt
ci: add test for component override features
2020-04-02 10:33:48 -04:00
(idf.py reconfigure | grep "overriden_dir:$IDF_PATH/components/esp32") || failure "Failed to get overriden dir" # no registration, overrides registration as well
print_status "Overriding Kconfig"
echo "idf_component_register(KCONFIG \${overriden_dir}/Kconfig)" >> components/esp32/CMakeLists.txt
echo "idf_component_get_property(kconfig \${COMPONENT_NAME} KCONFIG)" >> components/esp32/CMakeLists.txt
echo "message(STATUS kconfig:\${overriden_dir}/Kconfig)" >> components/esp32/CMakeLists.txt
(idf.py reconfigure | grep "kconfig:$IDF_PATH/components/esp32/Kconfig") || failure "Failed to verify original `main` directory"
rm -rf components
cmake: swap priority between EXTRA_COMPONENT_DIRS and project components
2021-03-16 05:39:16 -04:00
print_status "Project components prioritized over EXTRA_COMPONENT_DIRS"
clean_build_dir
mkdir -p extra_dir/my_component
echo "idf_component_register()" > extra_dir/my_component/CMakeLists.txt
cp CMakeLists.txt CMakeLists.bak # set EXTRA_COMPONENT_DIRS to point to the other directory
${SED} -i "s%cmake_minimum_required(VERSION \([0-9]\+\).\([0-9]\+\))%cmake_minimum_required(VERSION \1.\2)\nset(EXTRA_COMPONENT_DIRS extra_dir)%" CMakeLists.txt
(idf.py reconfigure | grep "$PWD/extra_dir/my_component") || failure "Unable to find component specified in EXTRA_COMPONENT_DIRS"
mkdir -p components/my_component
echo "idf_component_register()" > components/my_component/CMakeLists.txt
(idf.py reconfigure | grep "$PWD/components/my_component") || failure "Project components should be prioritized over EXTRA_COMPONENT_DIRS"
mv CMakeLists.bak CMakeLists.txt # revert previous modifications
rm -rf extra_dir components
add new command to idf
2020-09-03 05:16:42 -04:00
print_status "Create project using idf.py and build it"
echo "Trying to create project."
(idf.py -C projects create-project temp_test_project) || failure "Failed to create the project."
cd "$IDF_PATH/projects/temp_test_project"
echo "Building the project temp_test_project . . ."
idf.py build || failure "Failed to build the project."
cd "$IDF_PATH"
rm -rf "$IDF_PATH/projects/temp_test_project"
print_status "Create component using idf.py, create project using idf.py."
print_status "Add the component to the created project and build the project."
echo "Trying to create project . . ."
(idf.py -C projects create-project temp_test_project) || failure "Failed to create the project."
echo "Trying to create component . . ."
(idf.py -C components create-component temp_test_component) || failure "Failed to create the component."
${SED} -i '5i\\tfunc();' "$IDF_PATH/projects/temp_test_project/main/temp_test_project.c"
${SED} -i '5i#include "temp_test_component.h"' "$IDF_PATH/projects/temp_test_project/main/temp_test_project.c"
cd "$IDF_PATH/projects/temp_test_project"
idf.py build || failure "Failed to build the project."
cd "$IDF_PATH"
rm -rf "$IDF_PATH/projects/temp_test_project"
rm -rf "$IDF_PATH/components/temp_test_component"
print_status "Check that command for creating new project will fail if the target folder is not empty."
mkdir "$IDF_PATH/example_proj/"
touch "$IDF_PATH/example_proj/tmp_130698"
EXPECTED_EXIT_VALUE=3
expected_failure $EXPECTED_EXIT_VALUE idf.py create-project --path "$IDF_PATH/example_proj/" temp_test_project || failure "Command exit value is wrong."
rm -rf "$IDF_PATH/example_proj/"
print_status "Check that command for creating new project will fail if the target path is file."
touch "$IDF_PATH/example_proj"
EXPECTED_EXIT_VALUE=4
expected_failure $EXPECTED_EXIT_VALUE idf.py create-project --path "$IDF_PATH/example_proj" temp_test_project || failure "Command exit value is wrong."
rm -rf "$IDF_PATH/example_proj"
tools: Add docs subcommand docs which opens browser with documentation for current version of idf and model of your target Add docs subcommand with options: --no-browser - Prints url for current documentation instead of opens browser with documentation --language - Select documentation language --starting-page - Choice section of documentation to open --version - Choice version of esp-idf --target - Choice model of your target
2021-06-03 11:14:38 -04:00
print_status "Check docs command"
clean_build_dir
idf.py build
idf.py set-target esp32s2
idf.py docs || failure "'idf.py docs' failed"
idf.py docs --no-browser | grep "https://docs.espressif.com/projects/esp-idf/en" || failure "'idf.py docs --no-browser' failed"
idf.py docs --no-browser --language en | grep "https://docs.espressif.com/projects/esp-idf/en" || failure "'idf.py docs --no-browser --language en' failed"
idf.py docs --no-browser --language en --version v4.2.1 | grep "https://docs.espressif.com/projects/esp-idf/en/v4.2.1" || failure "'idf.py docs --no-browser --language en --version v4.2.1' failed"
idf.py docs --no-browser --language en --version v4.2.1 --target esp32 | grep "https://docs.espressif.com/projects/esp-idf/en/v4.2.1/esp32" || failure "'idf.py docs --no-browser --language en --version v4.2.1 --target esp32' failed"
idf.py docs --no-browser --language en --version v4.2.1 --target esp32 --starting-page get-started | grep "https://docs.espressif.com/projects/esp-idf/en/v4.2.1/esp32/get-started" || failure "'idf.py docs --no-browser --language en --version v4.2.1 --target esp32 --starting-page get-started' failed"
tools: replace _ with - in idf.py Closes https://github.com/espressif/esp-idf/issues/5126
2021-08-11 09:24:17 -04:00
print_status "Deprecation warning check"
ci: Fix build system tests to clean the dir
2021-11-26 00:23:14 -05:00
cd ${TESTDIR}/template
tools: replace _ with - in idf.py Closes https://github.com/espressif/esp-idf/issues/5126
2021-08-11 09:24:17 -04:00
# click warning
idf.py post_debug &> tmp.log
tools: Deprecated commands removed from idf.py Remove deprecated commands from idf.py, but they are still kept working as cmake deprecated targets.
2022-03-18 07:09:14 -04:00
grep "Error: Command \"post_debug\" is deprecated since v4.4 and was removed in v5.0." tmp.log || failure "Missing deprecation warning with command \"post_debug\""
tools: replace _ with - in idf.py Closes https://github.com/espressif/esp-idf/issues/5126
2021-08-11 09:24:17 -04:00
rm tmp.log
# cmake warning
idf.py efuse_common_table &> tmp.log
tools: Deprecated commands removed from idf.py Remove deprecated commands from idf.py, but they are still kept working as cmake deprecated targets.
2022-03-18 07:09:14 -04:00
grep "Have you wanted to run \"efuse-common-table\" instead?" tmp.log || failure "Missing deprecation warning with command \"efuse_common_table\""
tools: replace _ with - in idf.py Closes https://github.com/espressif/esp-idf/issues/5126
2021-08-11 09:24:17 -04:00
rm tmp.log
Tools: Add "idf.py save-defconfig" command to generate sdkconfig.defaults
2021-12-14 09:31:08 -05:00
print_status "Save-defconfig checks"
cd ${TESTDIR}/template
rm -f sdkconfig.defaults
rm -f sdkconfig
idf.py fullclean > /dev/null
echo "CONFIG_COMPILER_OPTIMIZATION_SIZE=y" >> sdkconfig
echo "CONFIG_ESPTOOLPY_FLASHFREQ_80M=y" >> sdkconfig
idf.py save-defconfig
wc -l sdkconfig.defaults
grep "CONFIG_IDF_TARGET" sdkconfig.defaults && failure "CONFIG_IDF_TARGET should not be in sdkconfig.defaults"
grep "CONFIG_COMPILER_OPTIMIZATION_SIZE=y" sdkconfig.defaults || failure "Missing CONFIG_COMPILER_OPTIMIZATION_SIZE=y in sdkconfig.defaults"
grep "CONFIG_ESPTOOLPY_FLASHFREQ_80M=y" sdkconfig.defaults || failure "Missing CONFIG_ESPTOOLPY_FLASHFREQ_80M=y in sdkconfig.defaults"
idf.py fullclean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
idf.py set-target esp32c3
echo "CONFIG_PARTITION_TABLE_OFFSET=0x8001" >> sdkconfig
idf.py save-defconfig
wc -l sdkconfig.defaults
grep "CONFIG_IDF_TARGET=\"esp32c3\"" sdkconfig.defaults || failure "Missing CONFIG_IDF_TARGET=\"esp32c3\" in sdkconfig.defaults"
grep "CONFIG_PARTITION_TABLE_OFFSET=0x8001" sdkconfig.defaults || failure "Missing CONFIG_PARTITION_TABLE_OFFSET=0x8001 in sdkconfig.defaults"
idf.py fullclean > /dev/null
rm -f sdkconfig.defaults
rm -f sdkconfig
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
print_status "All tests completed"
if [ -n "${FAILURES}" ]; then
echo "Some failures were detected:"
echo -e "${FAILURES}"
exit 1
else
echo "Build tests passed."
fi
}
function print_status()
{
echo "******** $1"
STATUS="$1"
}
function failure()
{
echo "!!!!!!!!!!!!!!!!!!!"
echo "FAILURE: $1"
echo "!!!!!!!!!!!!!!!!!!!"
FAILURES="${FAILURES}${STATUS} :: $1\n"
}
add new command to idf
2020-09-03 05:16:42 -04:00
function expected_failure() {
"${@:2}"
EXIT_VALUE=$?
if [ $EXIT_VALUE != "$1" ]; then
echo "[ERROR] Exit value of executed command is $EXIT_VALUE (expected $1)"; return 1
else return 0
fi
}
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
TESTDIR=${PWD}/build_system_tests_$$
mkdir -p ${TESTDIR}
# set NOCLEANUP=1 if you want to keep the test directory around
# for post-mortem debugging
[ -z ${NOCLEANUP} ] && trap "rm -rf ${TESTDIR}" EXIT KILL
SNAPSHOT=${TESTDIR}/snapshot
BUILD=${TESTDIR}/template/build
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
IS_DARWIN=
export SED=sed
export REALPATH=realpath
if [ "$(uname -s)" = "Darwin" ]; then
IS_DARWIN=1
export SED=gsed
export REALPATH=grealpath
fi
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
# copy all the build output to a snapshot directory
function take_build_snapshot()
{
rm -rf ${SNAPSHOT}
cp -ap ${TESTDIR}/template/build ${SNAPSHOT}
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
if [ -n "$IS_DARWIN" ]; then
# wait at least 1 second before the next build, for the test in
# file_was_rebuilt to work
sleep 1
fi
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
}
# verify that all the arguments are present in the build output directory
function assert_built()
{
until [ -z "$1" ]; do
if [ ! -f "${BUILD}/$1" ]; then
failure "File $1 should be in the build output directory"
fi
shift
done
}
# Test if a file has been rebuilt.
function file_was_rebuilt()
{
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
if [ -z "$IS_DARWIN" ]; then
# can't use [ a -ot b ] here as -ot only gives second resolution
# but stat -c %y seems to be microsecond at least for tmpfs, ext4..
if [ "$(stat -c %y ${SNAPSHOT}/$1)" != "$(stat -c %y ${BUILD}/$1)" ]; then
return 0
else
return 1
fi
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
else
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
# macOS: work around 1-second resolution by adding a sleep in take_build_snapshot
if [ ${SNAPSHOT}/$1 -ot ${BUILD}/$1 ]; then
return 0
else
return 1
fi
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
fi
}
# verify all the arguments passed in were rebuilt relative to the snapshot
function assert_rebuilt()
{
until [ -z "$1" ]; do
assert_built "$1"
if [ ! -f "${SNAPSHOT}/$1" ]; then
failure "File $1 should be in original build snapshot"
fi
if ! file_was_rebuilt "$1"; then
failure "File $1 should have been rebuilt"
fi
shift
done
}
# verify all the arguments are in the build directory & snapshot,
# but were not rebuilt
function assert_not_rebuilt()
{
until [ -z "$1" ]; do
assert_built "$1"
if [ ! -f "${SNAPSHOT}/$1" ]; then
failure "File $1 should be in snapshot build directory"
fi
if file_was_rebuilt "$1"; then
failure "File $1 should not have been rebuilt"
fi
shift
done
}
# do a "clean" that doesn't depend on idf.py
function clean_build_dir()
{
ci: fixes for CMake build system test on macOS
2019-10-30 13:36:51 -04:00
PRESERVE_ROOT_ARG=
if [ -z "$IS_DARWIN" ]; then
PRESERVE_ROOT_ARG=--preserve-root
fi
rm -rf $PRESERVE_ROOT_ARG ${BUILD}/* ${BUILD}/.*
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
}
ci: add build system tests for bootloader flash mode/freq/size
2020-01-23 06:20:22 -05:00
# check the bytes 3-4 of the binary image header. e.g.:
# bin_header_match app.bin 0210
function bin_header_match()
{
expected=$2
filename=$1
actual=$(xxd -s 2 -l 2 -ps $1)
if [ ! "$expected" = "$actual" ]; then
failure "Incorrect binary image header, expected $expected got $actual"
fi
}
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
cd ${TESTDIR}
run_tests
Reference in New Issue Copy Permalink