| RE: [cdt-dev] Mixed C/C++ in MBS |
|
Hi Doug, Here are the problems that I remember
right now: 1. The MBS project creation UI still
makes the user select a C project vs. a C++ project. The Tools in the
tool-chain of a project get “filtered” based upon the project
nature (C vs. C++). So, even though a tool-chain may contain both C and
C++ compilers, only one will be used for the project. There may be other
MBS logic that distinguishes between C and C++ natures, but I can’t
remember any off hand. 2. MBS now uses content types, and I
don’t know that the “case sensitivity” content type issues have
been resolved. See bugzillas 103530, 115388, and 105022. The current situation is that a user must
create a C or C++ project. The user can make a project-specific addition
to a content type – for example to be able to process .c files in a C++
project. However, those .c files will be compiled by the C++ compiler. Our intention is to address these problems
as part of the new “Project Model”, but we have no concrete plans
there yet. Regards, Leo From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Doug Schaefer Hey guys, I’m trying to figure out where we are with MBS
as I start to use it for our internal QNX toolchain. There was an issue with
having C files in C++ projects. Can someone update me on where we are with that
and whether you need my help addressing it? Thanks, Eclipse CDT Project Lead, http://cdtdoug.blogspot.com |