[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Indexer problems?
|
I see, you're right. We actually already had our own scanner config
discovery profile for other reasons, so I didn't realize it would also
be necessary in your case. I think you should replace:
class='org.eclipse.cdt.managedbuilder.internal.scannerconfig.DefaultGCCS
cannerInfoCollector'
with:
class='org.eclipse.cdt.managedbuilder.internal.scannerconfig.DefaultGnuW
inScannerInfoCollector'
in your extension. I remember it taking forever to get this right back
when I was working on this, but hopefully that's all you'll need to do.
Separately to the managed build developers: It seems weird that you
should have to define your own extension for this just to override the
command to run. Shouldn't it read the command from the toolchain itself
somehow? What if the user overrides the gcc command in the UI? It
doesn't seem that the scanner info stuff would realize that and would
continue to run gcc, even if the user switched it to arm-linux-gcc or
the like. I assume this would cause the indexer to be incorrect in this
case. Maybe I've missed something, though.
Jeremiah Lott
TimeSys Corporation
> -----Original Message-----
> From: dmsubs [mailto:dmsubs@xxxxxxxxxxxxx]
> Sent: Tuesday, February 28, 2006 1:02 PM
> To: Lott, Jeremiah; 'CDT General developers list.'
> Subject: RE: [cdt-dev] Indexer problems?
>
>
> Hi Jeremiah,
>
> That looks like it will solve my problem, but I can't work
> out how to put it
> into my plugin (sorry).
>
> If I just replace scannerConfigDiscoveryProfileId as you
> suggest, it is then
> trying to invoke 'gcc'. I guess I have to make a new scanner
> extension...
>
> My current scanner extension is defined as:
>
> <extension
> id='GCCManagedMakePerProjectProfile'
> name="%crt.arm.scanner"
>
> point='org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile'
> >
> <scannerInfoCollector
>
> class='org.eclipse.cdt.managedbuilder.internal.scannerconfig.D
> efaultGCCScann
> erInfoCollector'
> scope='project'
> />
> <scannerInfoProvider
> providerId='specsFile'
> >
> <run
> arguments='-E -P -v -dD
> ${plugin_state_location}/${specs_file}'
>
> class='org.eclipse.cdt.make.internal.core.scannerconfig2.GCCSp
> ecsRunSIProvid
> er'
> command="%crt.arm.scanner.command"
> />
> <scannerInfoConsoleParser
>
> class='org.eclipse.cdt.make.internal.core.scannerconfig.gnu.GC
> CSpecsConsoleP
> arser'
> />
> </scannerInfoProvider>
> </extension>
>
> Any suggestions gratefully received!
>
> Thanks
>
> ---
> Derek
>
> > -----Original Message-----
> > From: Lott, Jeremiah [mailto:jeremiah.lott@xxxxxxxxxxx]
> > Sent: 28 February 2006 16:15
> > To: dmsubs@xxxxxxxxxxxxx; CDT General developers list.
> > Subject: RE: [cdt-dev] Indexer problems?
> >
> > It automatically detects the built-in includes by running
> arm-elf-gcc.
> > If your compiler returns cygwin-style paths, then you need to
> > add an attribute like this to your toolchain:
> >
> > scannerConfigDiscoveryProfileId="org.eclipse.cdt.managedbuilde
> > r.core.GCC
> > WinManagedMakePerProjectProfile"
> >
> > This should cause those paths to be converted into
> > windows-style paths.
> > Hopefully this helps.
> >
> > Jeremiah Lott
> > TimeSys Corporation
> >
> > > -----Original Message-----
> > > From: cdt-dev-bounces@xxxxxxxxxxx
> > > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of dmsubs
> > > Sent: Tuesday, February 28, 2006 10:41 AM
> > > To: dmsubs@xxxxxxxxxxxxx; 'CDT General developers list.'; 'Doug
> > > Schaefer'
> > > Subject: RE: [cdt-dev] Indexer problems?
> > >
> > >
> > > Hi,
> > >
> > > No, it's not the spacey pathname problem...
> > >
> > > Doug, back to your original question. AFAIK, I haven't
> > specified paths
> > > anywhere (neither the plugin, nor in the project) I'm
> guessing that
> > > the the indexer (arm-elf-gcc) is reporting the path in a cygwin
> > > format, but something else is unable to interpret it that way. Is
> > > there a way to trace what is going on here?
> > >
> > > Thanks,
> > >
> > >
> > > ---
> > > Derek
> > >
> > > > -----Original Message-----
> > > > From: cdt-dev-bounces@xxxxxxxxxxx
> > > > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of dmsubs
> > > > Sent: 28 February 2006 15:25
> > > > To: 'Doug Schaefer'; 'CDT General developers list.'
> > > > Subject: RE: [cdt-dev] Indexer problems?
> > > >
> > > > Hi Doug,
> > > >
> > > > Hmm, I've just had a thought... I wonder if it is the 'spacey
> > > > pathname'
> > > > problem. I've installed into C:\Program Files\GNUARM). I'll
> > > > investigate.
> > > >
> > > > [I am using 3.1.2/3.0.2]
> > > >
> > > > Thanks
> > > > ---
> > > > Derek
> > > >
> > > > > -----Original Message-----
> > > > > From: Doug Schaefer [mailto:DSchaefer@xxxxxxx]
> > > > > Sent: 28 February 2006 15:18
> > > > > To: dmsubs@xxxxxxxxxxxxx; CDT General developers list.
> > > > > Subject: RE: [cdt-dev] Indexer problems?
> > > > >
> > > > > Just guessing, but it could be the cygwin paths that you
> > > are using.
> > > > > The CDT does not use cygpath to get at files. You need to
> > > > provide the
> > > > > paths as real Windows paths.
> > > > >
> > > > > Doug Schaefer, QNX Software Systems Eclipse CDT Project Lead,
> > > > > http://cdtdoug.blogspot.com
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: cdt-dev-bounces@xxxxxxxxxxx
> > > > > [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> > > > > > On Behalf Of dmsubs
> > > > > > Sent: Tuesday, February 28, 2006 10:08 AM
> > > > > > To: 'CDT General developers list.'
> > > > > > Subject: [cdt-dev] Indexer problems?
> > > > > >
> > > > > >
> > > > > > Hi
> > > > > >
> > > > > > I have defined a plugin for the GNUARM tools. When I
> > > create a new
> > > > > > (empty) project based on this plugin, I immediately get the
> > > > > following error:
> > > > > >
> > > > > > Invalid project path: Include path not found
> > > (\cygdrive\c\program
> > > > > > files\gnuarm\arm-elf\include).
> > > > > >
> > > > > > When I create a simple C "Hello World" program, and
> > > build it, the
> > > > > > program builds and links without error. However, after
> > > the clean
> > > > > > build, I still have the following errors reported in the
> > > > "Problems"
> > > > > > window:
> > > > > >
> > > > > > Invalid project path: Include path not found
> > > (\cygdrive\c\program
> > > > > > files\gnuarm\arm-elf\include).
> > > > > > Invalid project path: Include path not found
> > > (\cygdrive\c\program
> > > > > > files\gnuarm\arm-elf\sys-include).
> > > > > > Invalid project path: Include path not found
> > > (\cygdrive\c\program
> > > > > > files\gnuarm\lib\gcc\arm-elf\4.0.2\include).
> > > > > > C/C++ Indexer Problem: Preprocessor Inclusion not found:
> > > > > stdio.h in file:
> > > > > > C:\Workspace\hello\hello.c on line: 1.
> > > > > > C/C++ Indexer Problem: Preprocessor Inclusion not found:
> > > > > stdlib.h in file:
> > > > > > C:\Workspace\hello\hello.c on line: 2.
> > > > > >
> > > > > > together with Warnings in the editor window by each of the
> > > > > #includes
> > > > > > that
> > > > > > state:
> > > > > >
> > > > > > C/C++ Indexer Problem: Preprocessor Inclusion not found:
> > > > > stdio.h in file:
> > > > > > C:\Workspace\hello\hello.c on line: 1.
> > > > > >
> > > > > > Any clues as to what I am doing wrong?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > ---
> > > > > > Derek
> > > > > >
> > > > > > _______________________________________________
> > > > > > cdt-dev mailing list
> > > > > > cdt-dev@xxxxxxxxxxx
> > > > > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > > >
> > > > _______________________________________________
> > > > cdt-dev mailing list
> > > > cdt-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >
>
>
