The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
14 lines
357 B
YAML
14 lines
357 B
YAML
sample:
|
|
name: hello world
|
|
description: Hello World sample, the simplest Zephyr application
|
|
platforms: all
|
|
tests:
|
|
- test:
|
|
build_only: true
|
|
tags: samples tests
|
|
- singlethread:
|
|
build_only: true
|
|
extra_args: CONF_FILE=prj_single.conf
|
|
filter: not CONFIG_BT and not CONFIG_GPIO_SCH
|
|
tags: samples tests
|