zephyr

bartoszek/zephyr

Fork 0

Commit Graph

Author	SHA1	Message	Date
Tomasz Bursztyka	97326c0445	device: Fix structure attributes access Since struct devconfig was merged earlier into struct device, let's fix accessing config_info, name, ... attributes everywhere via: grep -rlZ 'dev->config->' \| xargs -0 sed -i 's/dev->config->/dev->/g' Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>	2020-05-08 23:07:44 +02:00
Torsten Rasmussen	407b49b35c	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-03-27 16:23:46 +01:00
Sebastian Bøe	011da8c1b0	samples: Add sample 'application_development/out_of_tree_driver' Add a sample that demonstrates (and tests) that custom drivers can be maintained outside of Zephyr. The sample is fairly minimal with few dependencies and should therefore be very portable. It also includes a sample.yaml that should ensure that it does not regress. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>	2020-01-22 09:26:12 -05:00

Author

SHA1

Message

Date

Tomasz Bursztyka

97326c0445

device: Fix structure attributes access

Since struct devconfig was merged earlier into struct device, let's fix
accessing config_info, name, ... attributes everywhere via:

grep -rlZ 'dev->config->' | xargs -0 sed -i 's/dev->config->/dev->/g'

Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>

2020-05-08 23:07:44 +02:00

Torsten Rasmussen

407b49b35c

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-03-27 16:23:46 +01:00

Sebastian Bøe

011da8c1b0

samples: Add sample 'application_development/out_of_tree_driver'

Add a sample that demonstrates (and tests) that custom drivers can be
maintained outside of Zephyr.

The sample is fairly minimal with few dependencies and should
therefore be very portable. It also includes a sample.yaml that should
ensure that it does not regress.

Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>

2020-01-22 09:26:12 -05:00

3 Commits