SES Compiling Blinky with GNU++11

[bernerj]

Hi,

I'm trying to include a library written in C++ which requires at least GNU++11. Unfortunately if I switch the C++ compiler in SES I get the following error:

2> In file included from ../nrf_SDK/components/ble/common/ble_srv_common.h:54,
2>                  from /Users/bernerj/Documents/SEGGER Embedded Studio for ARM Projects/ses-food-sensor/Application/main.cpp:54:
2> ../nrf_SDK/components/libraries/util/app_util.h:216:55: error: expected constructor, destructor, or type conversion before '(' token
2> ../nrf_SDK/components/libraries/util/app_util.h:237:62: note: in definition of macro '_SELECT_ASSERT_FUNC'
2> ../nrf_SDK/components/libraries/util/app_util.h:253:25: note: in expansion of macro 'STATIC_ASSERT_MSG'
2> ../nrf_SDK/components/softdevice/common/nrf_sdh_ble.h:83:1: note: in expansion of macro 'STATIC_ASSERT'
2> ../nrf_SDK/components/ble/nrf_ble_gatt/nrf_ble_gatt.h:71:1: note: in expansion of macro 'NRF_SDH_BLE_OBSERVER'
2> /Users/bernerj/Documents/SEGGER Embedded Studio for ARM Projects/ses-food-sensor/Application/main.cpp:92:1: note: in expansion of macro 'NRF_BLE_GATT_DEF'
2> ../nrf_SDK/components/libraries/util/app_util.h:216:55: error: expected constructor, destructor, or type conversion before '(' token
2> ../nrf_SDK/components/libraries/util/app_util.h:237:62: note: in definition of macro '_SELECT_ASSERT_FUNC'
2> ../nrf_SDK/components/libraries/util/app_util.h:253:25: note: in expansion of macro 'STATIC_ASSERT_MSG'
2> ../nrf_SDK/components/softdevice/common/nrf_sdh_ble.h:84:1: note: in expansion of macro 'STATIC_ASSERT'
2> ../nrf_SDK/components/ble/nrf_ble_gatt/nrf_ble_gatt.h:71:1: note: in expansion of macro 'NRF_SDH_BLE_OBSERVER'
2> /Users/bernerj/Documents/SEGGER Embedded Studio for ARM Projects/ses-food-sensor/Application/main.cpp:92:1: note: in expansion of macro 'NRF_BLE_GATT_DEF'
2> ../nrf_SDK/components/libraries/util/app_util.h:216:55: error: expected constructor, destructor, or type conversion before '(' token
2> ../nrf_SDK/components/libraries/util/app_util.h:237:62: note: in definition of macro '_SELECT_ASSERT_FUNC'
2> ../nrf_SDK/components/libraries/util/app_util.h:253:25: note: in expansion of macro 'STATIC_ASSERT_MSG'
2> ../nrf_SDK/components/softdevice/common/nrf_sdh_ble.h:83:1: note: in expansion of macro 'STATIC_ASSERT'
2> ../nrf_SDK/components/ble/nrf_ble_qwr/nrf_ble_qwr.h:74:5: note: in expansion of macro 'NRF_SDH_BLE_OBSERVER'
2> /Users/bernerj/Documents/SEGGER Embedded Studio for ARM Projects/ses-food-sensor/Application/main.cpp:93:1: note: in expansion of macro 'NRF_BLE_QWR_DEF'
2> ../nrf_SDK/components/libraries/util/app_util.h:216:55: error: expected constructor, destructor, or type conversion before '(' token
2> ../nrf_SDK/components/libraries/util/app_util.h:237:62: note: in definition of macro '_SELECT_ASSERT_FUNC'
2> ../nrf_SDK/components/libraries/util/app_util.h:253:25: note: in expansion of macro 'STATIC_ASSERT_MSG'
2> ../nrf_SDK/components/softdevice/common/nrf_sdh_ble.h:84:1: note: in expansion of macro 'STATIC_ASSERT'
2> ../nrf_SDK/components/ble/nrf_ble_qwr/nrf_ble_qwr.h:74:5: note: in expansion of macro 'NRF_SDH_BLE_OBSERVER'

Is there a way to fix this? 

[Jørgen Holmefjord]

Hi,

Our SDK does not support C++ and has not been tested with C++ compilers. I think the simples solution would be to keep the main file as a C-file and create a C API for your C++ library to expose the functionality. Maybe this post will help you.

Best regards,
Jørgen

[bernerj]

Okay that makes sense, but as I understand the softdevice itself does support C++ is this correct?

[Nguyen Hoan Hoang]

SES does not support C++.  It stripped out C++ support from GCC.  I recommend using Eclipse with GCC for full C++ supports with the SDK.  See this blog embeddedsoftdev.blogspot.com/.../ehal-nrf51.html

[Jørgen Holmefjord]

This is from the softevice specifications:

"The SoftDevice Application Programming Interface (API) is available to applications as a C programming language interface based on Supervisor Call (SVC)s and defined in a set of header files."

You do not compile any part of the softdevice yourself, it comes as a precompiled binary. You just use the API to make calls inside the softdevice. The API may be compatible with some C++ compilers, but this is not something we guarantee. Most of the header files will wrap the defines in 'extern "C"', which should make it callable from C++ applications.

[bernerj]

ah yes, thanks for clearing this up