Re: [cdt-dev] Re: Build2 unveiling assumptions

[Andrew Gvozdev <angvoz.dev@xxxxxxxxx>]

CDT still can handle 3.0 projects which aren't tied to configurations (.cdtproject) but I believe it creates some kind of default ICConfigurationDescription out of it and feeds that into the system. It uses the old UI which is still there but dormant. Not sure if it is worth to try reusing that old UI.

Andrew

On Tue, May 4, 2010 at 10:12 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:

OK, I can relax now. Turns out to be PermGen space issues when I have Android projects. It's probably not related to CDT at all.

But still, if my thought was to allow for projects that don't use .cproject, but have a simpler data store (i.e. project preferences), and avoid the whole ICProjectDesc thing, I don't see how this can happen without digging through the whole CDT.

Anyway, sorry for the spam.

:D

On Tue, May 4, 2010 at 9:04 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:

OMG, ICConfigurationDescription is everywhere. And I'm getting an out of memory error when opening the editor on a new C++ file when I don't set one up. This is killing me...

On Tue, May 4, 2010 at 7:48 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:

I've got a start on my new build system. I'm seeing a number of exceptions that reveal assumptions that every project has configurations in the ICProjectDescription. I fear how much of that has spread.

At any rate, I'll be committing code that works around those assumptions with appropriate bug reports.

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