Should I use "Treat C files as C++ files"?

Eddie3909

I'm converting code from the DM642 to the DM648 and I get a lot of "undefined symbols" during link. The issue seems to be that the dm642 project was built using the "Treat C files as C++ files (-fg)" compiler switch. If I try using the -fg for the dm648, I get "undefined symbols" for the vport, i2c, and edma libraries.

Which would be better: 1) add #ifdef __cplusplus extern "C" to my .h files, or 2) re-compile all the libraries. Seems like adding extern "C" would be better since re-compiling all the vport, i2c and edma libraries -fg would make the libraries incompatible with my other programs. Am I seeing the choices correctly? Are there more?

Cheers
Eddie

over 15 years ago

0 Bernie Thompson TI over 15 years ago

TI__Mastermind 41665 points

In general the solution to working with C and C++ code at the same time has always been the first option of "#ifdef __cplusplus extern "C" { #endif ..." on C function declarations. However this should already be in place on the DM642 headers, at least it appears in some of the provided headers, this also seems to apply to DM648, so I assume you are referring to custom header files in this case.

0 Eddie3909 over 15 years ago in reply to Bernie Thompson TI

Guru 10385 points

Yes, these are custom headers that I've inherited and merging.

Thanks, I'll use the __cplusplus option.[8-|]

Cheers

Processors

Processors forum

Should I use "Treat C files as C++ files"?