bluetooth stack not cpp conform?

[hf81-ble]

I need to build project with cpp support. But is bluetooth really not cpp conform? i'm using zepyhr 3.3.0

G:/Projekte/nrf/zephyrproject/zephyr/include/zephyr/bluetooth/bluetooth.h:725:37: error: taking address of temporary array
  725 |         ((struct bt_le_adv_param[]) { \
      |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
  726 |                 BT_LE_ADV_PARAM_INIT(_options, _int_min, _int_max, _peer) \
      |                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  727 |          })
      |          ~~
G:/Projekte/nrf/zephyrproject/zephyr/include/zephyr/bluetooth/bluetooth.h:792:34: note: in expansion of macro 'BT_LE_ADV_PARAM'
  792 | #define BT_LE_EXT_ADV_NCONN_NAME BT_LE_ADV_PARAM(BT_LE_ADV_OPT_EXT_ADV | \
      |                                  ^~~~~~~~~~~~~~~
G:/Projekte/bycon/nrf-rt-tx-extension/src/main.cpp:130:36: note: in expansion of macro 'BT_LE_EXT_ADV_NCONN_NAME'
  130 |         err = bt_le_ext_adv_create(BT_LE_EXT_ADV_NCONN_NAME, NULL, &adv);
      |                                    ^~~~~~~~~~~~~~~~~~~~~~~~
G:/Projekte/nrf/zephyrproject/zephyr/include/zephyr/bluetooth/bluetooth.h:877:41: error: taking address of temporary array
  877 |         ((struct bt_le_per_adv_param[]) { \
      |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
  878 |                 BT_LE_PER_ADV_PARAM_INIT(_int_min, _int_max, _options) \
      |                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  879 |         })
      |         ~~
G:/Projekte/nrf/zephyrproject/zephyr/include/zephyr/bluetooth/bluetooth.h:881:31: note: in expansion of macro 'BT_LE_PER_ADV_PARAM'
  881 | #define BT_LE_PER_ADV_DEFAULT BT_LE_PER_ADV_PARAM(BT_GAP_PER_ADV_SLOW_INT_MIN, \
      |                               ^~~~~~~~~~~~~~~~~~~
G:/Projekte/bycon/nrf-rt-tx-extension/src/main.cpp:137:44: note: in expansion of macro 'BT_LE_PER_ADV_DEFAULT'
  137 |         err = bt_le_per_adv_set_param(adv, BT_LE_PER_ADV_DEFAULT);
      |                                            ^~~~~~~~~~~~~~~~~~~~~
G:/Projekte/nrf/zephyrproject/zephyr/include/zephyr/bluetooth/bluetooth.h:849:47: error: taking address of temporary array
  849 |         ((struct bt_le_ext_adv_start_param[]) { \
      |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
  850 |                 BT_LE_EXT_ADV_START_PARAM_INIT((_timeout), (_n_evts)) \
      |                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  851 |         })
      |         ~~
G:/Projekte/nrf/zephyrproject/zephyr/include/zephyr/bluetooth/bluetooth.h:853:37: note: in expansion of macro 'BT_LE_EXT_ADV_START_PARAM'
  853 | #define BT_LE_EXT_ADV_START_DEFAULT BT_LE_EXT_ADV_START_PARAM(0, 0)
      |                                     ^~~~~~~~~~~~~~~~~~~~~~~~~
G:/Projekte/bycon/nrf-rt-tx-extension/src/main.cpp:152:40: note: in expansion of macro 'BT_LE_EXT_ADV_START_DEFAULT'
  152 |         err = bt_le_ext_adv_start(adv, BT_LE_EXT_ADV_START_DEFAULT);
      |                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~

[hermabe]

What are your compile flags? Compound literals are a GCC extension in C++. https://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html

As an extension, GCC supports compound literals also in C90 mode and in C++, although as explained below, the C++ semantics are somewhat different.

[hermabe]

How are the bluetooth examples tested with cpp ?

As far as I know they are not tested with cpp upstream.

[hf81-ble]

in that case zephyr with bluetooth is not usable with C++? That is really bad and a showstopper to our current projects, because our middleware and application is already written in C++. (=> ok, that is our problem)

but in general to the zephyr project:

as i followed to my researches, that is a bug in the GCC compiler.
https://stackoverflow.com/questions/32941846/c-error-taking-address-of-temporary-array

[hermabe]

I am not sure what the general policy is in regards to C-specific things in headers. You could probably open a PR to ifdef out the c++-incompatible stuff. Maybe ask in #cpp in the discord how this is done generally.

[hermabe]

You might get away without an error if you dont use the predefined macros and set the struct members yourself.

[hf81-ble]

yes it worked by init the config struct manually:

//err = bt_le_ext_adv_create(BT_LE_EXT_ADV_NCONN_NAME, NULL, &adv); //cpp not working
	const bt_le_adv_param config1 = 
	{
		.id = BT_ID_DEFAULT, 
		.sid = 0, 
		.secondary_max_skip = 0, 
		.options = (BT_LE_ADV_OPT_EXT_ADV | BT_LE_ADV_OPT_USE_NAME), 
		.interval_min = (BT_GAP_ADV_FAST_INT_MIN_2), 
		.interval_max = (BT_GAP_ADV_FAST_INT_MAX_2), 
		.peer = (NULL), 
	};
		
	err = bt_le_ext_adv_create(&config1, NULL, &adv);