Re: [cdt-dev] What triggers indexing if not a build?

["J. Johnston" <jjohnstn@xxxxxxxxxx>]

We have a toolchain set up in our Build definition called:
GNU Autotools Toolchain and that is used for the Autotools projects.

It specifies: org.eclipse.cdt.make.core.GCCStandardMakePerFileProfile
for the scannerConfigDiscoveryProfileId field.

Is there something else we should check for?  I can include the build 
definition if that would be of any help.

-- Jeff J.

On 05/05/2010 09:39 PM, Andrew Gvozdev wrote:
> Did you create the project using "Other toolchain" by any chance? If a
> toolchain is not specified scanner discovery profile is not defined
> either. Do you get correct profile specified in Discovery Options?
>
> Andrew
>
> On Wed, May 5, 2010 at 7:20 PM, J. Johnston <jjohnstn@xxxxxxxxxx
> <mailto:jjohnstn@xxxxxxxxxx>> wrote:
>
>     Using the C Project Wizard, a ManagedBuild hello world C project
>     works fine.  A Makefile project created with a Makefile and a simple
>     source file, doesn't resolve the headers even after the build is
>     performed.
>
>     FWIW: an Autotools project sets supportsManagedBuild to false in its
>     build definition.
>
>     Autotools uses the Common Builder to do the make portion of the
>     build so the ScannerDiscovery is done there successfully, but the
>     data isn't saved across the sessions.
>
>     -- Jeff J.
>
>
>     On 05/05/2010 05:30 PM, Doug Schaefer wrote:
>
>         Do regular C++ projects work for you? or is this just a problem with
>         Autotools projects?
>
>         On Wed, May 5, 2010 at 5:14 PM, Jeff Johnston
>         <jjohnstn@xxxxxxxxxx <mailto:jjohnstn@xxxxxxxxxx>
>         <mailto:jjohnstn@xxxxxxxxxx <mailto:jjohnstn@xxxxxxxxxx>>> wrote:
>
>             I am trying out the latest M7 CDT (checked out in my local
>         Eclipse)
>             under Helios M7 with the Autotools plugin also checked out.
>
>             I start a child Eclipse instance and create an Autotools
>         project.
>               The header files for my source (a hello world program) are
>         unresolved.
>
>             I then start a build and the header files are then
>         resolved..i.e. I
>             can click on them in the outline view (includes stdio.h).  If I
>             highlight a function (e.g. "puts") in my source file and click
>             F3...nothing happens.  If I then right-click on the project
>         and do
>             an Index->Rebuild, the F3 action on puts now works successfully.
>
>             If I close the child Eclipse instance down and restart it,
>             everything happens over again.  Header files are
>         unresolved...need
>             to build again, and then I have to do a rebuild of the index
>         to get
>             indexing to work.
>
>             I don't see anything missing in the project settings for the
>         indexer
>             (it is enabled for the workspace).
>
>             Any ideas on why this is happening?
>
>             -- Jeff J.
>             _______________________________________________
>             cdt-dev mailing list
>         cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
>         <mailto:cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>>
>
>         https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>
>
>         _______________________________________________
>         cdt-dev mailing list
>         cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
>         https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>     _______________________________________________
>     cdt-dev mailing list
>     cdt-dev@xxxxxxxxxxx <mailto: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