zephyr/tests/misc/test_build/newlib.conf

CONFIG_DEBUG=y
CONFIG_STDOUT_CONSOLE=y
CONFIG_NEWLIB_LIBC=y
# turn bluetooth of until we resolve printf formatter
# difference between newlib & min-libc
CONFIG_BT=n
tests: add build tests for various options This test builds the syncronisation app using the following config options to verify if the build is successful: - CONFIG_DEBUG - CONFIG_NEWLIB_LIBC Change-Id: Idf2fe948ab58982244b3590da938a83206103be3 Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-01-20 13:17:33 +08:00			`CONFIG_DEBUG=y`
			`CONFIG_STDOUT_CONSOLE=y`
			`CONFIG_NEWLIB_LIBC=y`
tests: newlib: disable bluetooth for now When trying to build with newlib we get: hci_driver.c: In function 'hci_driver_open': hci_driver.c:389:10: error: format '%d' expects argument of type 'int', but argument 2 has type 'uint32_t {aka long unsigned int}' [-Werror=format=] BT_ERR("Required RAM size: %d, supplied: %u.", err, ^ This is because we have different types for {u}int32_t between newlib and mini-libc. We have to decide how we are going to handle this going forward. Various options include use of PRIu32, making mini-libc match newlib's types, disabling the -Werror=format, etc. Change-Id: I5df8fa05dd7658e1f6b2eeb8fa84e3270f3dd208 Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2017-01-24 21:55:02 +08:00			`# turn bluetooth of until we resolve printf formatter`
			`# difference between newlib & min-libc`
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* 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> 2017-08-09 14:21:11 +08:00			`CONFIG_BT=n`