yuzu-emu/mbedtls
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
mbedtls/programs/test/CMakeLists.txt

92 lines
3.5 KiB
CMake
Raw Normal View History

- Adapted CMake files for the PKCS#11 support
2011-01-18 17:18:38 +01:00
set(libs
Build: Add MBEDTLS_TARGET_PREFIX Allows required targets to have prefixes added to them, so that external projects can avoid target names clashing. Signed-off-by: Raef Coles <raef.coles@arm.com>
2020-10-13 17:30:41 +02:00
${mbedtls_target}
- Adapted CMake files for the PKCS#11 support
2011-01-18 17:18:38 +01:00
)
programs: cmake: Use list of executables Use list of executables to: - factorize the code to define executables - highlight the similarities and differences of the executable definitions - avoid list duplication Use alphabetic order for executables in lists. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 11:15:31 +02:00
set(executables_libs
Add a metatest program This program can be used to validate that things that should be detected as test failures are indeed caught, either by setting the test result to MBEDTLS_TEST_RESULT_FAILED or by aborting the program. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-11-02 18:48:39 +01:00
metatest
Test the PSA alternative header configuration macros Test that MBEDTLS_PSA_CRYPTO_PLATFORM_FILE and MBEDTLS_PSA_CRYPTO_STRUCT_FILE can be set to files in a directory that comes after the standard directory in the include file search path. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-22 22:09:51 +01:00
query_included_headers
programs: cmake: Use list of executables Use list of executables to: - factorize the code to define executables - highlight the similarities and differences of the executable definitions - avoid list duplication Use alphabetic order for executables in lists. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 11:15:31 +02:00
selftest
udp_proxy
)
- Added CMake makefiles as alternative to regular Makefiles. - Added preliminary Code Coverage tests for AES, ARC4, Base64, MPI, SHA-family, MD-family and HMAC-SHA-family.
2009-06-28 23:50:27 +02:00
programs: cmake: Use list of executables Use list of executables to: - factorize the code to define executables - highlight the similarities and differences of the executable definitions - avoid list duplication Use alphabetic order for executables in lists. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 11:15:31 +02:00
set(executables_mbedcrypto
benchmark
query_compile_time_config
zeroize
)
- Added CMake makefiles as alternative to regular Makefiles. - Added preliminary Code Coverage tests for AES, ARC4, Base64, MPI, SHA-family, MD-family and HMAC-SHA-family.
2009-06-28 23:50:27 +02:00
Change the cpp test to be optional Remove unnecessary defines from the test. Test by defining TEST_CPP using makefiles or cmake.
2018-03-15 10:16:24 +01:00
if(TEST_CPP)
Generate cpp_cummy_build.cpp dynamically Generate programs/test/cpp_dummy_build.cpp dynamically instead of maintaining it manually. This removes the need to update it when the list of headers changes. Include all the headers unconditionally except for the ones that cannot be included directly. Support this dynamic generation both with make and with cmake. Adapt all.sh accordingly. Remove the redundant C build from component_build_default_make_gcc_and_cxx (it was also done in component_test_default_out_of_box), leaving a component_test_make_cxx. Also run the C++ program, because why not. Do this in the full configuration which may catch a bit more problems in headers. Fixes #2570 for good. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-07-09 15:19:28 +02:00
set(cpp_dummy_build_cpp "${CMAKE_CURRENT_BINARY_DIR}/cpp_dummy_build.cpp")
set(generate_cpp_dummy_build "${CMAKE_CURRENT_SOURCE_DIR}/generate_cpp_dummy_build.sh")
add_custom_command(
OUTPUT "${cpp_dummy_build_cpp}"
COMMAND "${generate_cpp_dummy_build}" "${cpp_dummy_build_cpp}"
DEPENDS "${generate_cpp_dummy_build}"
WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}"
)
add_executable(cpp_dummy_build "${cpp_dummy_build_cpp}")
target_include_directories(cpp_dummy_build PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/../../include)
target_link_libraries(cpp_dummy_build ${mbedcrypto_target})
Change the cpp test to be optional Remove unnecessary defines from the test. Test by defining TEST_CPP using makefiles or cmake.
2018-03-15 10:16:24 +01:00
endif()
Don't build dlopen when building for Windows Windows doesn't have dlopen, not even Linux emulation environments such as MinGW. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-04 15:18:00 +01:00
if(USE_SHARED_MBEDTLS_LIBRARY AND
NOT ${CMAKE_SYSTEM_NAME} MATCHES "[Ww][Ii][Nn]")
New test app for dynamic loading of libmbed* with dlopen Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-04 12:45:19 +01:00
add_executable(dlopen "dlopen.c")
target_include_directories(dlopen PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/../../include)
Use CMake's knowledge of what system library has dlopen() Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-10 19:10:27 +01:00
target_link_libraries(dlopen ${CMAKE_DL_LIBS})
New test app for dynamic loading of libmbed* with dlopen Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-04 12:45:19 +01:00
endif()
Rename DEV_MODE to GEN_FILES GEN_FILES is a bit clearer as it describes what the setting does more precisely. Signed-off-by: David Horstmann <david.horstmann@arm.com>
2021-10-20 18:14:23 +02:00
if(GEN_FILES)
Introduce "Dev mode" option When the option is On, CMake will have rules to generate the generated files using scripts etc. When the option is Off, CMake will assume the files are available from the source tree; in that mode, it won't require any extra tools (Perl for example) compared to when we committed the files to git. The intention is that users will never need to adjust this option: - in the development branch (and features branches etc.) the option is always On (development mode); - in released tarballs, which include the generated files, we'll switch the option to Off (release mode) in the same commit that re-adds the generated files. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-09-08 13:27:09 +02:00
find_package(Perl REQUIRED)
Allow CMake to generate query_config.c This one was trickier for two reasons: 1. It's used from another directory, see https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#how-can-i-add-a-dependency-to-a-source-file-which-is-generated-in-a-subdirectory 2. The C file being generated after CMake is run means CMake can't automatically scan for included headers and do its usual magic, so we need to declare the dependency and more importantly the include path. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:07:33 +02:00
Introduce "Dev mode" option When the option is On, CMake will have rules to generate the generated files using scripts etc. When the option is Off, CMake will assume the files are available from the source tree; in that mode, it won't require any extra tools (Perl for example) compared to when we committed the files to git. The intention is that users will never need to adjust this option: - in the development branch (and features branches etc.) the option is always On (development mode); - in released tarballs, which include the generated files, we'll switch the option to Off (release mode) in the same commit that re-adds the generated files. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-09-08 13:27:09 +02:00
add_custom_command(
OUTPUT
${CMAKE_CURRENT_BINARY_DIR}/query_config.c
COMMAND
${PERL}
${CMAKE_CURRENT_SOURCE_DIR}/../../scripts/generate_query_config.pl
${CMAKE_CURRENT_SOURCE_DIR}/../../include/mbedtls/mbedtls_config.h
Fix query_config.c generation with CMake build system In case of an out-of-tree build with the CMake build system the path to crypto_config.h has to be defined as the path to mbedtls_config.h. Add this possibility tp generate_query_config.pl. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2023-08-30 17:36:25 +02:00
${CMAKE_CURRENT_SOURCE_DIR}/../../include/psa/crypto_config.h
Introduce "Dev mode" option When the option is On, CMake will have rules to generate the generated files using scripts etc. When the option is Off, CMake will assume the files are available from the source tree; in that mode, it won't require any extra tools (Perl for example) compared to when we committed the files to git. The intention is that users will never need to adjust this option: - in the development branch (and features branches etc.) the option is always On (development mode); - in released tarballs, which include the generated files, we'll switch the option to Off (release mode) in the same commit that re-adds the generated files. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-09-08 13:27:09 +02:00
${CMAKE_CURRENT_SOURCE_DIR}/../../scripts/data_files/query_config.fmt
${CMAKE_CURRENT_BINARY_DIR}/query_config.c
DEPENDS
Allow CMake to generate query_config.c This one was trickier for two reasons: 1. It's used from another directory, see https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#how-can-i-add-a-dependency-to-a-source-file-which-is-generated-in-a-subdirectory 2. The C file being generated after CMake is run means CMake can't automatically scan for included headers and do its usual magic, so we need to declare the dependency and more importantly the include path. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:07:33 +02:00
${CMAKE_CURRENT_SOURCE_DIR}/../../scripts/generate_query_config.pl
${CMAKE_CURRENT_SOURCE_DIR}/../../include/mbedtls/mbedtls_config.h
Fix query_config.c generation with CMake build system In case of an out-of-tree build with the CMake build system the path to crypto_config.h has to be defined as the path to mbedtls_config.h. Add this possibility tp generate_query_config.pl. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2023-08-30 17:36:25 +02:00
${CMAKE_CURRENT_SOURCE_DIR}/../../include/psa/crypto_config.h
Allow CMake to generate query_config.c This one was trickier for two reasons: 1. It's used from another directory, see https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#how-can-i-add-a-dependency-to-a-source-file-which-is-generated-in-a-subdirectory 2. The C file being generated after CMake is run means CMake can't automatically scan for included headers and do its usual magic, so we need to declare the dependency and more importantly the include path. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:07:33 +02:00
${CMAKE_CURRENT_SOURCE_DIR}/../../scripts/data_files/query_config.fmt
Introduce "Dev mode" option When the option is On, CMake will have rules to generate the generated files using scripts etc. When the option is Off, CMake will assume the files are available from the source tree; in that mode, it won't require any extra tools (Perl for example) compared to when we committed the files to git. The intention is that users will never need to adjust this option: - in the development branch (and features branches etc.) the option is always On (development mode); - in released tarballs, which include the generated files, we'll switch the option to Off (release mode) in the same commit that re-adds the generated files. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-09-08 13:27:09 +02:00
)
Fix assorted spelling and wording issues Signed-off-by: David Horstmann <david.horstmann@arm.com>
2021-10-20 13:29:47 +02:00
# this file will also be used in another directory, so create a target, see
Introduce "Dev mode" option When the option is On, CMake will have rules to generate the generated files using scripts etc. When the option is Off, CMake will assume the files are available from the source tree; in that mode, it won't require any extra tools (Perl for example) compared to when we committed the files to git. The intention is that users will never need to adjust this option: - in the development branch (and features branches etc.) the option is always On (development mode); - in released tarballs, which include the generated files, we'll switch the option to Off (release mode) in the same commit that re-adds the generated files. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-09-08 13:27:09 +02:00
# https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#how-can-i-add-a-dependency-to-a-source-file-which-is-generated-in-a-subdirectory
add_custom_target(generate_query_config_c
DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/query_config.c)
else()
link_to_source(query_config.c)
endif()
Allow CMake to generate query_config.c This one was trickier for two reasons: 1. It's used from another directory, see https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#how-can-i-add-a-dependency-to-a-source-file-which-is-generated-in-a-subdirectory 2. The C file being generated after CMake is run means CMake can't automatically scan for included headers and do its usual magic, so we need to declare the dependency and more importantly the include path. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:07:33 +02:00
programs: cmake: Use list of executables Use list of executables to: - factorize the code to define executables - highlight the similarities and differences of the executable definitions - avoid list duplication Use alphabetic order for executables in lists. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 11:15:31 +02:00
foreach(exe IN LISTS executables_libs executables_mbedcrypto)
cmake: Fix added sources to targets In cmake version < 3.0, the SOURCES property on targets cannot be modified after the target is defined. There are several instances in the code that were using `target_properties()`, which is not available in the older versions of cmake. Unfortunately, the workaround in #3801 (381c1078fc) assumes that this SOURCES property can be modified. Work around this by building up any necessary sources before declaring the target. This is more awkward, but needed to continue to be able to support the old versions of cmake. Fixes #3788. Signed-off-by: David Brown <david.brown@linaro.org>
2020-11-18 23:07:24 +01:00
set(extra_sources "")
if(exe STREQUAL "query_compile_time_config")
list(APPEND extra_sources
Allow CMake to generate query_config.c This one was trickier for two reasons: 1. It's used from another directory, see https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#how-can-i-add-a-dependency-to-a-source-file-which-is-generated-in-a-subdirectory 2. The C file being generated after CMake is run means CMake can't automatically scan for included headers and do its usual magic, so we need to declare the dependency and more importantly the include path. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:07:33 +02:00
${CMAKE_CURRENT_SOURCE_DIR}/query_config.h
${CMAKE_CURRENT_BINARY_DIR}/query_config.c)
cmake: Fix added sources to targets In cmake version < 3.0, the SOURCES property on targets cannot be modified after the target is defined. There are several instances in the code that were using `target_properties()`, which is not available in the older versions of cmake. Unfortunately, the workaround in #3801 (381c1078fc) assumes that this SOURCES property can be modified. Work around this by building up any necessary sources before declaring the target. This is more awkward, but needed to continue to be able to support the old versions of cmake. Fixes #3788. Signed-off-by: David Brown <david.brown@linaro.org>
2020-11-18 23:07:24 +01:00
endif()
add_executable(${exe} ${exe}.c $<TARGET_OBJECTS:mbedtls_test>
${extra_sources})
Remove certs module from mbedtls. Certs will be used only by tests and programs. Signed-off-by: Mateusz Starzyk <mateusz.starzyk@mobica.com>
2021-02-08 15:34:42 +01:00
target_include_directories(${exe} PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/../../tests/include)
Allow CMake to generate query_config.c This one was trickier for two reasons: 1. It's used from another directory, see https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#how-can-i-add-a-dependency-to-a-source-file-which-is-generated-in-a-subdirectory 2. The C file being generated after CMake is run means CMake can't automatically scan for included headers and do its usual magic, so we need to declare the dependency and more importantly the include path. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:07:33 +02:00
if(exe STREQUAL "query_compile_time_config")
target_include_directories(${exe} PRIVATE ${CMAKE_CURRENT_SOURCE_DIR})
endif()
Add test utility udp_proxy Currently just forwards: will delay, duplicate and drop later.
2014-09-04 14:55:28 +02:00
programs: cmake: Use list of executables Use list of executables to: - factorize the code to define executables - highlight the similarities and differences of the executable definitions - avoid list duplication Use alphabetic order for executables in lists. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 11:15:31 +02:00
# This emulates "if ( ... IN_LIST ... )" which becomes available in CMake 3.3
list(FIND executables_libs ${exe} exe_index)
if (${exe_index} GREATER -1)
target_link_libraries(${exe} ${libs})
else()
Build: Add MBEDTLS_TARGET_PREFIX Allows required targets to have prefixes added to them, so that external projects can avoid target names clashing. Signed-off-by: Raef Coles <raef.coles@arm.com>
2020-10-13 17:30:41 +02:00
target_link_libraries(${exe} ${mbedcrypto_target})
programs: cmake: Use list of executables Use list of executables to: - factorize the code to define executables - highlight the similarities and differences of the executable definitions - avoid list duplication Use alphabetic order for executables in lists. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 11:15:31 +02:00
endif()
endforeach()
Add programs/test/zeroize.c to test mbedtls_zeroize The idea is to use the simple program that is expected to be modified rarely to set a breakpoint in a specific line and check that the function mbedtls_zeroize() does actually set the buffer to 0 and is not optimised out by the compiler.
2017-10-24 22:10:45 +02:00
programs: cmake: Use list of executables Use list of executables to: - factorize the code to define executables - highlight the similarities and differences of the executable definitions - avoid list duplication Use alphabetic order for executables in lists. Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 11:15:31 +02:00
install(TARGETS ${executables_libs} ${executables_mbedcrypto}
- Added install targets to the CMake files
2011-01-05 16:07:54 +01:00
DESTINATION "bin"
PERMISSIONS OWNER_READ OWNER_WRITE OWNER_EXECUTE GROUP_READ GROUP_EXECUTE WORLD_READ WORLD_EXECUTE)
Reference in a new issue Copy permalink