• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 2687 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Invalid project path: Duplicate path entries.

MikeH
Guru 15580 points


Can someone explain what this means and how to fix it?

Invalid project path: Duplicate path entries.

I have already tried importing my project into a new workspace, but it has the same warning/error.

Thx,

MikeH

 

  • 0
    TI__Guru**** 171309 points

    MikeH,

    I've seen this issue before in some of my projects but unfortunately I don't recall how I solved it - maybe I recreated the project from scratch, but I don't know.

    I searched around and it seems there is a known bug in the Eclipse CDT:

    https://bugs.eclipse.org/bugs/show_bug.cgi?id=158940

    And stack overflow has a somewhat radical solution to it:

    http://stackoverflow.com/questions/307367/eclipse-cdt-invalid-project-path

    Unfortunately this issue happened to me only randomly, but I will try to take note on the solution if I hit it again. 

    Sorry for not being of much help,

    Rafael

  • 0 in reply to desouza
    Guru 15580 points

    Rafael,

    Thanks for following up. Here is some interesting dialog from the Eclipse bug tracker.

    Eclipse bug tracker log said:

    I've recently run into (I think) this same issue while implementing scanner discovery for my tool chain.  In my case I have two tools, a compiler and an assembler, that each have their own built in macros. Some of these macros, however, are the same for both tools (i.e. __PRODUCTVERSION__=1234). When validating the resolved path entries the PathEntryManager seems to lump them all into one list and then complains that they are duplicates even though they apply to two completely different inputTypes.  This results in a case where a user sees an alarming warning that they can do nothing about and that has no adverse impact on their project.

    And....

    Eclipse bug tracker log said:

    CDT is an open source project driven by community efforts. Unfortunately nobody feels this is important enough to invest their time and fix it given the difficulty of the task. I think you underestimate it but feel free to prove me wrong and post a patch. Just make sure that patch corrects the real problem and not just disables diagnostic message.

    Thx,

    MikeH