Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Is it ok to break the build of CDT on 3.5?

This usually happens every release. Usually we just ask for vetos in case someone is using the old CDT with the new Platform. But even those vetos should be only short term

So any vetos on breaking CDT 6.0 on Platform 3.6? (none from me BWT).

Doug.

On Thu, Oct 1, 2009 at 10:39 AM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
Hi,

with 3.6M2 platform gives us a way to have asynchronous commands.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=284363
Using this means that if a command is taking a long time, the UI won't hang.

As part of bug 275687 (Reverse commands block the UI thread)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=275687
I've migrated the Reverse Debugging commands (reverse steps, reverse resume, etc)
to this new infrastructure.  Also, I moved these commands from DSF-GDB down to
cdt.debug.ui to allow for other integrations to use them.

The problem is that if I check-in that patch, some plugins will no longer build
with 3.5, you would need 3.6M2.

I wondered what is our approach to this?
This patch is in no way urgent, but I'd like to eventually commit it.

Any guidance?

Thanks


Marc

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top