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

16 lines
555 B
CMake
Raw Normal View History

tests/subsys/fs/littlefs: add tests Verify all FS API calls using the nRF52840 development kit. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2019-08-01 00:34:44 +08:00
# SPDX-License-Identifier: Apache-2.0
cmake_minimum_required(VERSION 3.13.1)
tests: make find_package(Zephyr...) REQUIRED ... because it is (required). This makes a difference when building with CMake and forgetting ZEPHYR_BASE or not registering Zephyr in the CMake package registry. In this particular case, REQUIRED turns this harmless looking log statement: -- Could NOT find Zephyr (missing: Zephyr_DIR) -- The C compiler identification is GNU 9.3.0 -- The CXX compiler identification is GNU 9.3.0 -- Check for working C compiler: /usr/bin/cc -- ... -- ... -- ... -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at CMakeLists.txt:8 (target_sources): Cannot specify sources for target "app" which is not built by this project. ... into this louder, clearer, faster and (last but not least) final error: CMake Error at CMakeLists.txt:5 (find_package): Could not find a package configuration file provided by "Zephyr" with any of the following names: ZephyrConfig.cmake zephyr-config.cmake Add the installation prefix of "Zephyr" to CMAKE_PREFIX_PATH or set "Zephyr_DIR" to a directory containing one of the above files. If "Zephyr" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-05-29 08:58:50 +08:00
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
tests/subsys/fs/littlefs: add tests Verify all FS API calls using the nRF52840 development kit. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2019-08-01 00:34:44 +08:00
project(littlefs)
FILE(GLOB app_sources src/*.c)
tests/subsys/fs: Add fs_open flags tests to LittleFS The addition of support for open flags, within fs_open, requires addition of new test cases. Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
2020-06-19 22:29:47 +08:00
# LittleFS opens files for RW by default if no flags given and crashes,
# instead of returning error when attempting to perform operation that
# a file has not been opened for.
target_compile_definitions(app PRIVATE
BYPASS_FS_OPEN_FLAGS_LFS_ASSERT_CRASH
BYPASS_FS_OPEN_FLAGS_LFS_RW_IS_DEFAULT
)
target_sources(app PRIVATE ${app_sources} ../common/test_fs_open_flags.c)