From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Tuesday, February 27, 2007
6:44 PM
To: CDT
General developers list.
Subject: RE: [cdt-dev] discouraged
access in CDT-plugins
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail
Sent: Tuesday, February 27, 2007
10:11 AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] discouraged
access in CDT-plugins
Hi Doug,
> From my point of
view, thought, I just want the internal builder working again…
What problems with
Internal Builder have appeared with the New Project model? Is it https://bugs.eclipse.org/bugs/show_bug.cgi?id=175198? If so, I’m going to address it ASAP. I
just did not understand from the bug report that this was due to the New
Project Model check-in.
[Doug>] I am assuming so, it works fine in M5. I am also
concerned that the dependency checking isn’t working, but I’ll have
to conform that. There’s also https://bugs.eclipse.org/bugs/show_bug.cgi?id=175581
which prevents the index features from working with Windows C++ projects.
It’s not internal builder but my main concern is really to ensure the
MSVC and MinGW integrations work. Both rely on the internal builder. And since
I’m so dependant on it, I will certainly help fix bugs there once I get
my Windows debugger further along.
> and to make
sure my customers’ standard make projects don’t blow up when they
migrate to CDT 4.
Since I’ve
received no feed-back on the proposed backward compatibility support for Build
System API (https://bugs.eclipse.org/bugs/show_bug.cgi?id=115935#c89), I assume everyone agrees on
that, so I’m going to implement the proposed approach this week.
[Doug>] Please contact Dave Inglis at QNX directly. He
has lots of feedback J. Our QNX
projects are built on top of the IMakeBuildInfo and other standard make APIs.
These APIs, from what I can see, were built somewhat specifically to support
the design decisions we made when QNX projects were created, which predates
managed make. I’m pretty sure we’ll be the most impacted by the
decision to turn standard make projects into managed make.
BTW, I’m just nervous. This is certainly the biggest
change in the CDT since we first introduced the indexer in 2.0, and it’s
pretty fundamental to a lot of people. By my measure, most users have been
using standard make, especially ones that pay money J. We’ll
need to do a lot of testing to ensure their projects can move forward without
issue. And we also need a plan to allow them to move backwards if issues do
come up.