OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/misc/check_init_priorities/CMakeLists.txt

28 lines
940 B
CMake
Raw Normal View History

test: misc: add a test application for check_init_priorities Add a test specifically for the check_init_priorities scripts. The test creates a set of fake devices to exercise the three possible conditions, run a build, run the check script and validate the script output. The check is meant to fail the build on error but that's bypassed in this case as that would fail the twister run. That specific bit is covered in unit tests anyway. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-03-29 23:35:44 +08:00
# SPDX-License-Identifier: Apache-2.0
cmake_minimum_required(VERSION 3.20.0)
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
set(output_file ${PROJECT_BINARY_DIR}/check_init_priorities_output.txt)
scripts: check_init_priorities: use the Zephyr executable file Rework check_init_priorities to use the main executable file instead of the individual object files for discovering the devices. This should make the script more robust in case of stale files in the build directory, and also makes it work with LTO object files. Additionally, keep track of the detected init calls, and add a handy "-i" option to produce a human readable print of the initcalls in the call sequence, which can be useful for debugging initialization problems due to odd SYS_INIT and DEVICE interactions. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-09-09 02:10:13 +08:00
add_custom_command(
test: misc: add a test application for check_init_priorities Add a test specifically for the check_init_priorities scripts. The test creates a set of fake devices to exercise the three possible conditions, run a build, run the check script and validate the script output. The check is meant to fail the build on error but that's bypassed in this case as that would fail the twister run. That specific bit is covered in unit tests anyway. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-03-29 23:35:44 +08:00
COMMENT "Running check_init_priorities.py"
scripts: check_init_priorities: use the Zephyr executable file Rework check_init_priorities to use the main executable file instead of the individual object files for discovering the devices. This should make the script more robust in case of stale files in the build directory, and also makes it work with LTO object files. Additionally, keep track of the detected init calls, and add a handy "-i" option to produce a human readable print of the initcalls in the call sequence, which can be useful for debugging initialization problems due to odd SYS_INIT and DEVICE interactions. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-09-09 02:10:13 +08:00
OUTPUT ${output_file}
tests/misc/check_init_priorities: Fix for native_sim Fix this test for the native_simulator, and add it as a default test target. Also be a bit clearer in stdout about the test having passed or not. Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
2023-11-23 20:31:06 +08:00
DEPENDS
${logical_target_for_zephyr_elf}
$<$<TARGET_EXISTS:native_runner_executable>:native_runner_executable>
test: misc: add a test application for check_init_priorities Add a test specifically for the check_init_priorities scripts. The test creates a set of fake devices to exercise the three possible conditions, run a build, run the check script and validate the script output. The check is meant to fail the build on error but that's bypassed in this case as that would fail the twister run. That specific bit is covered in unit tests anyway. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-03-29 23:35:44 +08:00
COMMAND ${PYTHON_EXECUTABLE} ${ZEPHYR_BASE}/scripts/build/check_init_priorities.py
tests/misc/check_init_priorities: Fix for native_sim Fix this test for the native_simulator, and add it as a default test target. Also be a bit clearer in stdout about the test having passed or not. Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
2023-11-23 20:31:06 +08:00
--elf-file=$<IF:$<TARGET_EXISTS:native_runner_executable>,${BYPRODUCT_KERNEL_EXE_NAME},${BYPRODUCT_KERNEL_ELF_NAME}>
test: misc: add a test application for check_init_priorities Add a test specifically for the check_init_priorities scripts. The test creates a set of fake devices to exercise the three possible conditions, run a build, run the check script and validate the script output. The check is meant to fail the build on error but that's bypassed in this case as that would fail the twister run. That specific bit is covered in unit tests anyway. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-03-29 23:35:44 +08:00
--verbose
--output ${output_file}
--always-succeed
COMMAND ${PYTHON_EXECUTABLE} ${APPLICATION_SOURCE_DIR}/validate_check_init_priorities_output.py
${output_file}
)
scripts: check_init_priorities: use the Zephyr executable file Rework check_init_priorities to use the main executable file instead of the individual object files for discovering the devices. This should make the script more robust in case of stale files in the build directory, and also makes it work with LTO object files. Additionally, keep track of the detected init calls, and add a handy "-i" option to produce a human readable print of the initcalls in the call sequence, which can be useful for debugging initialization problems due to odd SYS_INIT and DEVICE interactions. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-09-09 02:10:13 +08:00
add_custom_target(check_init_priorities_output ALL DEPENDS ${output_file})
test: misc: add a test application for check_init_priorities Add a test specifically for the check_init_priorities scripts. The test creates a set of fake devices to exercise the three possible conditions, run a build, run the check script and validate the script output. The check is meant to fail the build on error but that's bypassed in this case as that would fail the twister run. That specific bit is covered in unit tests anyway. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-03-29 23:35:44 +08:00
project(check_init_priorities)
target_sources(app PRIVATE src/main.c)