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.

CCS 4.2.3 Invalid project description



When importing projects in code composer 4.2.3, some of the library projects refuse to import due eclipse overlap file error:

 When looking at the files to choose, the ones that fail have an absolute (not relative) description  :

How should I resolve this?

 

  • Looks like a bug in Eclipse.  Or maybe not a bug, but just weird behavior.

    Looking at the code, this situation will happen when the project you’re importing is already physically inside the workspace directory, and the project’s name (LibFpgaMessagesEdm) does not match the project’s root folder name (LibFpgaMessages). 

    There are two ways I can think of to work around this problem:

    1. If the user is OK with making changes to the project, just rename the project’s root folder to match the project name (rename the folder C:/ProjectFiles/auto2/LibFpgaMessages to “C:/ProjectFiles/auto2/LibFpgaMessagesEdm”).  Then import as usual. 
    2. If the user is not OK with making changes to the project, then create a new workspace (in a new location), then import the project from its current location (C:/ProjectFiles/auto2/LibFpgaMessages), and make sure you don’t select the “Copy into workspace” checkbox. 

    I'd go with #1, if possible, to avoid running into this situation again.

    - Baltasar

  • Solution number 1 seems to have fixed the problem. So, in particular, when converting a 3.1 project where the name is different from the folder, one needs to be careful to rename them the same. Thanks for your help.