mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-10 23:53:16 +00:00
Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no> |
||
---|---|---|
.. | ||
src | ||
CMakeLists.txt | ||
Makefile | ||
prj.conf | ||
README.txt | ||
testcase.yaml |
Title: test_aes_ccm Description: This test verifies that the TinyCrypt AES APIs operate as expected. -------------------------------------------------------------------------------- Building and Running Project: This project outputs to the console. It can be built and executed on QEMU as follows: make run -------------------------------------------------------------------------------- Troubleshooting: Problems caused by out-dated project information can be addressed by issuing one of the following commands then rebuilding the project: make clean # discard results of previous builds # but keep existing configuration info or make pristine # discard results of previous builds # and restore pre-defined configuration info -------------------------------------------------------------------------------- Sample Output: tc_start() - Performing CCM tests: Performing CCM test #1 (RFC 3610 test vector #1): =================================================================== PASS - do_test. Performing CCM test #2 (RFC 3610 test vector #2): =================================================================== PASS - do_test. Performing CCM test #3 (RFC 3610 test vector #3): =================================================================== PASS - do_test. Performing CCM test #4 (RFC 3610 test vector #7): =================================================================== PASS - do_test. Performing CCM test #5 (RFC 3610 test vector #8): =================================================================== PASS - do_test. Performing CCM test #6 (RFC 3610 test vector #9): =================================================================== PASS - do_test. Performing CCM test #7 (no associated data): =================================================================== PASS - test_vector_7. Performing CCM test #8 (no payload data): =================================================================== PASS - test_vector_8. All CCM tests succeeded! =================================================================== PASS - main. =================================================================== PROJECT EXECUTION SUCCESSFUL