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

46 lines
1.6 KiB
CMake
Raw Normal View History

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
crypto_examples
key_ladder_demo
psa_constant_names
)
psa: programs: Add cipher example Add `programs/psa/crypto_examples.c`. Update relevant Makefiles, CMakeLists.txt, and .gitignore files.
2018-07-10 09:10:21 +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
if(DEV_MODE)
add_custom_command(
OUTPUT
${CMAKE_CURRENT_BINARY_DIR}/psa_constant_names_generated.c
COMMAND
Use MBEDTLS_PYTHON_EXECUTABLE Change one occurrence of ${PYTHON} to ${MBEDTLS_PYTHON_EXECUTABLE} and add implied ${MBEDTLS_PYTHON_EXECUTABLE} to the start of a different command. Signed-off-by: David Horstmann <david.horstmann@arm.com>
2021-10-20 17:53:58 +02:00
${MBEDTLS_PYTHON_EXECUTABLE}
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/generate_psa_constants.py
${CMAKE_CURRENT_BINARY_DIR}
WORKING_DIRECTORY
${CMAKE_CURRENT_SOURCE_DIR}/../..
DEPENDS
Allow CMake to generate psa_constant_names_generated.c This one's a bit funny too as the generated file is not a source to the executable (ie, it's not passed as an argument to the compiler), so CMake's dependency resolution didn't work even though the file is in the same directory. For some reason, the following didn't work either: add_dependencies(psa_constant_names ${CMAKE_CURRENT_BINARY_DIR}/psa_constant_names_generated.c) So, apply the same strategy as for cross-directory use of a generated file by creating a target and using it as a dependency. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:33:32 +02:00
${CMAKE_CURRENT_SOURCE_DIR}/../../scripts/generate_psa_constants.py
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}/../../include/psa/crypto_values.h
${CMAKE_CURRENT_SOURCE_DIR}/../../include/psa/crypto_extra.h
)
else()
link_to_source(psa_constant_names_generated.c)
endif()
Allow CMake to generate psa_constant_names_generated.c This one's a bit funny too as the generated file is not a source to the executable (ie, it's not passed as an argument to the compiler), so CMake's dependency resolution didn't work even though the file is in the same directory. For some reason, the following didn't work either: add_dependencies(psa_constant_names ${CMAKE_CURRENT_BINARY_DIR}/psa_constant_names_generated.c) So, apply the same strategy as for cross-directory use of a generated file by creating a target and using it as a dependency. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
2021-05-14 10:33:32 +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)
programs: Link to tests common code Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 16:00:22 +02:00
add_executable(${exe} ${exe}.c $<TARGET_OBJECTS:mbedtls_test>)
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: Link to tests common code Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2020-06-05 16:00:22 +02:00
target_include_directories(${exe} PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/../../tests/include)
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
endforeach()
CMake: build and install key_ladder_demo
2019-01-02 17:28:46 +01:00
Generate PSA constant names in CMake build dir This commit modifies the generate_psa_constants.py script to take as input argument the location of where to write the psa_constant_names_generated.c file. For make-based build system, this commit does not change anything. For CMake build system, this commit modifies the generation location of that file to be inside the build directory and include it from there in psa_constant_names.c Fix #3365 Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
2020-05-28 09:42:01 +02:00
target_include_directories(psa_constant_names PRIVATE ${CMAKE_CURRENT_BINARY_DIR})
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
if(DEV_MODE)
add_custom_target(generate_psa_constant_names_generated_c
DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/psa_constant_names_generated.c)
add_dependencies(psa_constant_names generate_psa_constant_names_generated_c)
endif()
CMake: psa_constant_names and test_psa_constant_names Build and install psa_constant_names. Make sure that test_psa_constant_names passes in an out-of-tree build.
2019-01-02 17:29:04 +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
install(TARGETS ${executables}
psa: programs: Add cipher example Add `programs/psa/crypto_examples.c`. Update relevant Makefiles, CMakeLists.txt, and .gitignore files.
2018-07-10 09:10:21 +02:00
DESTINATION "bin"
PERMISSIONS OWNER_READ OWNER_WRITE OWNER_EXECUTE GROUP_READ GROUP_EXECUTE WORLD_READ WORLD_EXECUTE)
CMake: build and install key_ladder_demo
2019-01-02 17:28:46 +01:00
install(PROGRAMS
key_ladder_demo.sh
DESTINATION "bin")
Reference in a new issue Copy permalink