Re: [cdt-dev] Getting started with CDT dev

[Marc-Andre Laperle <malaperle@xxxxxxxxx>]

On 17/10/2012 5:14 PM, Chris Stankevitz wrote:
> On Wed, Oct 17, 2012 at 12:32 PM, Marc Khouzam
> <marc.khouzam@xxxxxxxxxxxx> wrote:
> > A trick that I use is that I do _not_ install CDT on the eclipse
> > I will work on CDT in.  That way, the only CDT that will run when
> > I test is the projects I have imported.
> > If you do install CDT, then you don't have to import all projects
> > because the compiler will use the installation for anything
> > that is missing.  But then you don't have the latest code for
> > you compilation.  So, it is safer not to install CDT for your
> > development env.
>
> Marc,
>
> I attempted to take your advice by
> a. Not installing the CDT on my CDT development installation
> b. Not setting an API baseline on my CDT development installation

I think Marc meant to say he installs CDT in a separate Eclipse 
installation altogether, not his Eclipse SDK. Sometimes, I actually just 
download the "Eclipse for C/C++ developers" from the main download page 
and set my baseline to that, since it will contains all the "core stuff" 
I work on. It also gives me a easy way to test something with the 
"older" version.


> 10. First 100 errors (filtered):
> BadParseException cannot be resolved to a type
> BadParseSymFileException cannot be resolved to a type
> Bundle 'net.sourceforge.lpg.lpgjavaruntime' cannot be resolved
> Bundle 'org.eclipse.rse.core' cannot be resolved
> Bundle 'org.eclipse.rse.files.ui' cannot be resolved
> Bundle 'org.eclipse.rse.services' cannot be resolved
> Bundle 'org.eclipse.rse.subsystems.files.core' cannot be resolved
> Bundle 'org.eclipse.rse.subsystems.shells.core' cannot be resolved
> Bundle 'org.eclipse.rse.ui' cannot be resolved
> Bundle 'org.eclipse.test.performance' cannot be resolved
> ConfigurationElement cannot be resolved to a type
> ConfigurationStack cannot be resolved to a type
> DiagnoseParser cannot be resolved to a type


It looks like you imported a lot if not all the CDT plugins from the git 
repo. You probably don't need all of this for the bug you want to fix. I 
would start by adding this:

org.eclipse.cdt.codan.checkers
org.eclipse.cdt.codan.checkers.ui
org.eclipse.cdt.codan.core
org.eclipse.cdt.codan.core.cxx
org.eclipse.cdt.codan.internal.ui.cxx
org.eclipse.cdt.codan.ui
org.eclipse.cdt.codan.ui.cfgview
org.eclipse.cdt.core
org.eclipse.cdt.core.tests
org.eclipse.cdt.core.linux
org.eclipse.cdt.core.linux.x86_64
org.eclipse.cdt.debug.core
org.eclipse.cdt.debug.mi.core
org.eclipse.cdt.debug.mi.ui
org.eclipse.cdt.debug.ui
org.eclipse.cdt.dsf
org.eclipse.cdt.dsf.gdb
org.eclipse.cdt.dsf.gdb.ui
org.eclipse.cdt.dsf.ui
org.eclipse.cdt.gdb
org.eclipse.cdt.gdb.ui
org.eclipse.cdt.launch
org.eclipse.cdt.make.core
org.eclipse.cdt.make.ui
org.eclipse.cdt.managedbuilder.core
org.eclipse.cdt.managedbuilder.gnu.ui
org.eclipse.cdt.managedbuilder.ui
org.eclipse.cdt.ui
org.eclipse.cdt.ui.tests


Then add whatever missing bundle it's complaining about. You shouldn't 
need RSE or test.performance unless you want to look at remote launching 
and run tests for debugging. Indexing and parsing is in cdt.core.

Hope this helps,

Marc-Andre