zephyr/samples/drivers/ht16k33/CMakeLists.txt

# SPDX-License-Identifier: Apache-2.0

cmake_minimum_required(VERSION 3.13.1)

find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})
project(ht16k33)

FILE(GLOB app_sources src/*.c)
target_sources(app PRIVATE ${app_sources})
samples: drivers: ht16k33: add sample application for the HT16K33 Add a sample application for showcasing the functionality of the Holtek HT16K33 LED driver with keyscan functionality. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk> 2019-03-25 03:24:31 +08:00			`# SPDX-License-Identifier: Apache-2.0`

			`cmake_minimum_required(VERSION 3.13.1)`

cmake: use find_package to locate Zephyr Using find_package to locate Zephyr. Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate code. Whenever an automatic run of CMake happend by the build system / IDE then it was required that ZEPHYR_BASE was defined. Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to cache the base variable and thus allowing subsequent invocation even if ZEPHYR_BASE is not set in the environment. It also removes the risk of strange build results if a user switchs between different Zephyr based project folders and forgetting to reset ZEPHYR_BASE before running ninja / make. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> 2020-02-12 22:00:46 +08:00			`find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})`
samples: drivers: ht16k33: add sample application for the HT16K33 Add a sample application for showcasing the functionality of the Holtek HT16K33 LED driver with keyscan functionality. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk> 2019-03-25 03:24:31 +08:00			`project(ht16k33)`

			`FILE(GLOB app_sources src/*.c)`
			`target_sources(app PRIVATE ${app_sources})`