C++ eclipse compilation

RE: C++ eclipse compilation

tesc — Thu, 07 Jul 2016 14:41:17 GMT

Yes, among the included files is RTT_Syscalls_GCC.c.

RE: C++ eclipse compilation

jean.oriano — Thu, 07 Jul 2016 12:37:06 GMT

I tried with sample and keil, the sysCall files isnt the same, the function inside too. I want to use it with eclipse so i use sysCallgcc file.

RE: C++ eclipse compilation

tesc — Wed, 06 Jul 2016 12:40:13 GMT

Hi,

RTT files are included in the latest SDK (11.0.0), under (sdk folder)/external/segger_rtt. Some of the SDK examples uses RTT, in particular for logging (nrf_log library). If the RTT files are included in the SDK you are using then I suggest you stick to them rather than fetching a potentially different version from segger.

When that is said, I do have some vague memories of getting similar errors myself. I do not remember what I did to fix it, but if you enable RTT logging for an SDK example and get that to work you should at least have some idea what a working setup looks like.

Regarding C++ libraries (or rather, their size) microcontrollers in general have limited program memory and are traditionally programmed in C. This means most lightwight and μc libraries are written in C. Also C++ libraries have not been subject to the same size limitations as have C libraries. Add to this that some string manipulations are complex operations, and you will see why string libraries are so large. I am sure someone would suggest a library if you state what operations you need.

Regards, Terje

RE: C++ eclipse compilation

jean.oriano — Tue, 05 Jul 2016 13:59:38 GMT

I found an other post : post and i downloaded the latest Jlink code source. There is the same code. There are the sames errors.

I dont understand why they tried to "overload" the initial function but it doesn't work.

RE: C++ eclipse compilation

Eirik Midttun — Tue, 05 Jul 2016 10:55:16 GMT

What string operations do you need? Could you do what you want with string.h (C library) and wrap it into C++?

RE: C++ eclipse compilation

Eirik Midttun — Tue, 05 Jul 2016 10:54:08 GMT

Check this post at the SEGGER forum: Conflicting types in SEGGER_RTT_Syscalls_GCC.c. There seems to be a signedness probleme in the library. SEGGER should answer to this.

For the second problem, yes, adding standard libraries can give you a huge penalty on memory usage. It is quite common to not use them and implement simpler libraries that matches the requirements for the product, that is needed features and available memory.

Did you do try compiling with optimizations? Could be worth trying. But in general I think iostream is an overkill.

RE: C++ eclipse compilation

jean.oriano — Tue, 05 Jul 2016 10:47:16 GMT

for the second problem, the lib c++ iostream is too big. i tried with the lib c++ string and it works. But it's not ok. my software .hex was 30ko size and after including this lib, it was 230ko size.

is it light c++ libraries for µController ?

RE: C++ eclipse compilation

jean.oriano — Tue, 05 Jul 2016 10:10:13 GMT

For the first problem, i only add the following code for includind lib c :

#ifdef __cplusplus

extern "C" {  

#endif

#include "SEGGER_RTT.h"


#ifdef __cplusplus

}

#endif

-----> doesn't work !!

RE: C++ eclipse compilation

jean.oriano — Tue, 05 Jul 2016 09:56:32 GMT

I didn't write this. I download it from segger website. This file is a c file. But, u can have c and c++ file in a c++ project ?

RE: C++ eclipse compilation

Eirik Midttun — Tue, 05 Jul 2016 09:51:06 GMT

@jean.oriano Did you write SEGGER_RTT_Syscalls_GCC.c? I don't recognize it from the SEGGER RTT files. Also, it is uncertain to what extent you are using C++. Could be that SEGGER is not written with C++ in mind.

RE: C++ eclipse compilation

tesc — Tue, 05 Jul 2016 08:54:21 GMT

What exactly is the problem? Can you update your question to include the error messages?