emWin + Redlib + C++

[lpcware]

Content originally posted in LPCWare by n6hpa on Wed Mar 05 01:03:38 MST 2014
I posted this in the microprocessor forum for the 1788 but I think that was the wrong spot...

I am trying to start a C++ project that uses emWin, and I see that all of the binaries distributed by NXP for LPCXpresso use redlib which does not work with C++ projects. Is it possible to get the NXP provided libraries to work in C++ or do I need to go to SEGGER directly for support?

For background I'm using the EA OEM kit for the 1788 with the 320x240 LCD.

Thanks in advance!

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 06 07:34:10 MST 2014

---

Quote: n6hpa
….. redlib documentation explicitly states that it is not compatible with C++, but I have not found out why.

---

Redlib is an implementation of the C90 standard C library (with some C99 extensions). It does not implement C++ library functionality. To get C++ library functionality, you therefore need to link against Newlib.

http://www.lpcware.com/content/faq/lpcxpresso/redlib-and-newlib

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by n6hpa on Thu Mar 06 05:07:49 MST 2014
To further clarify, I am primarily interested in the following possible responses:

A: "Someone has successfully developed a C++ application using emWin and linking the libemWin_522_LPCXpresso510_M3_LE_Redlib_d5.a library"
B: "I know for a fact that A is impossible because of X"

[lpcware]

Content originally posted in LPCWare by n6hpa on Thu Mar 06 04:55:40 MST 2014
The reason that I "jumped" to the conclusion that the problem was the library is that the redlib documentation explicitly states that it is not compatible with C++, but I have not found out why.  I didn't realize that my OEM board didn't come with debug functionality, so I ordered my debug probe last week and it hasn't arrived yet.  Clearly it takes time to get a productive answer on this forum (hint hint I haven't got one yet) so why does it hurt to ask the question now?

Maybe you should join the rest of us in any century by being a decent human being and only respond to forum posts if you have meaningful input.  You could also try joining the average 5 year old and READ my previous response where I indicated that I have already determined that the emWin function calls are crashing and I won't know more details until my debugger arrives.

[lpcware]

Content originally posted in LPCWare by TheFallGuy on Thu Mar 06 04:35:28 MST 2014
So you have no idea why it is crashing, so you immediately jump to the conclusion that the problem lies in the C/C++ library?

Get yourself a debug probe (LPC-Link2 costs $20), and join the rest of us in the 20th century by debugging your application... (yes, 20th, not 21st). You'll save yourself and everybody else a lot of time.

[lpcware]

Content originally posted in LPCWare by n6hpa on Wed Mar 05 22:57:59 MST 2014
I already tried and it didn't work. It compiles and links but it crashes on boot up. Once I get a debugger I'll be able to figure out where it's crashing but it is definitely crashing somewhere in the emWin function calls.

[lpcware]

Content originally posted in LPCWare by TheFallGuy on Wed Mar 05 01:30:46 MST 2014
Redlib and Newlib are just C libraries - as defined by the standard. I can't see how emWin (which works on a large number of tools from different vendors) can be dependent on a particular C library from NXP.

Why not try it, and if you find a problem, post to the forum. I am sure somebody will help!