Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Indexer isn't saving Includes across sessions 
On 17/11/09 06:31 PM, Doug Schaefer wrote:

How did the include paths get there, i.e., was it populate by scanner
discovery? If so, I've seen this too with the Android native projects
I've been trying, although at times they did stay.
Yes, sorry not to clarify. I am using the CDT's GCCStandardMakePerFileProfile (hope I spelled that correctly). 


I'd check the .cproject file to make sure the includes were stored
there, and if not, figure out why they aren't getting added correctly.
If they are in the .cproject file, then that's just weird.

Again, the architecture of this stuff makes it really hard to debug
what's going on. But a few guys on the list here are becoming experts on
it :).
Thanks. There is another reply here which notes a bug and a possible work-around. 

-- Jeff J.


Doug.

On Tue, Nov 17, 2009 at 5:27 PM, Jeff Johnston <jjohnstn@xxxxxxxxxx
<mailto:jjohnstn@xxxxxxxxxx>> wrote:

    I have an Autotools project which is based on a Makefile project.
      It has a tool-chain that includes the cdt gcc and cdt g++ compiler
    tools.

    When a project is first built, everything works fine with the
    indexer. There is an Includes container and it contains either the C
    or C++ include paths, depending on the type of project.

    The problem is when the session is closed, the include data seems to
    disappear.  When the session is restarted, the Includes container is
    missing and the indexer starts to warn about unknown include files.

    If the project is cleaned and rebuilt again, everything is back to
    normal.

    I have seen this behavior for 6.0.0 and 6.0.1.  Is there anything
    somebody could recommend to look at as to why the Includes aren't
    being saved across sessions?

    -- Jeff J.
    _______________________________________________
    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

Back to the top