How to tell CubeIDE to compile specific *.c files with C++ compiler ?

[ferro]

Hi,

How to tell CubeIDE to compile specific *.c files with C++ compiler ?

Changing suffix from *.c to *.cpp is not an option.

[edit] Changing the suffix from *.c to *.cpp is the least preferred option.

Thank you

[Andrew Neil]

---

@ferro wrote:

Changing suffix from *.c to *.cpp is not an option.

 

 Why not?  Seems misleading to name it .c when it's actually C++ ?

Anyhow, Could you just #include  the .c file in a .cpp file, and exclude the .c file from build?

[ferro]

Thanks for prompt reply.

No, files are writen in C and want to compile with C++ compiler.

"Could you just #include the .c file in a .cpp file, and exclude the .c file from build?"

Good idea but I perefere to set it as a flag in project properties. In Keil uVision IDE you right click on a file and set the  option to build it as C or C++.

[Andrew Neil]

If you right-click the file and choose 'Properties', there's this:

Looks like generic Eclipse ?

 

[Pavel A.]

@ferro You already know about the -x switch of the GNU compiler. Use it. Compiler options can be modified per file.

/* disclaimer: this should not be taken as advise to mix C++ into Cube-generated main.c and compile Cube generated  C files in C++ mode */

[ferro]

"Compiler options can be modified per file."

Where, how ?

[unsigned_char_array]

You can exclude the c file from build and include it in a new cpp file. That's an ugly workaround.

 

---

@ferro wrote:

"Compiler options can be modified per file."

Where, how ?

---

Rightclick the file. Click properties. Click C/C++ General. Click Language mappings. Then select GNU C++ from the drop down menus.

[Ozone]

C is basically a subset of C++, so a C souces should compile within a C++ project without issues.
They linkage is quite different (including startup file).
I suppose you are aware of the name mangling issue and the extern "C" statement in this context.

[ferro]

Thanks for comment, I would like to know how to configure CubeIDE.

[unsigned_char_array]

You can exclude the file from build and build it separately using a make file. You can run this command prior to building as an extra build step. Then add the o-file to the linker: https://community.st.com/t5/stm32-mcus-products/how-to-link-an-already-generated-object-file-in-existing-project/m-p/124589/highlight/true#M22428

[ferro]

Uf, this sounds scary. Seems the least annoying option is to change suffix to cpp, CubeIDE auto assign compiler based on that. And it's not possible to change it per file.

[unsigned_char_array]

---

@ferro wrote:

Uf, this sounds scary. Seems the least annoying option is to change suffix to cpp, CubeIDE auto assign compiler based on that. And it's not possible to change it per file.

---

Your first post said it was impossible to change the file extension. And now it suddenly is?

[ferro]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=282163

 

https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Freference%2Fcdt_u_prop_general_lng.htm

 

[unsigned_char_array]

And what happened? Can you show your build log?

[ferro]

Here, the original C recipe is used despite setting C++ in mapping.

I''ll come back later with a document describing what is going on.