• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 3937 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 warning

Chad Christensen
Expert 1670 points


I'm receiving the following warnings after compiling each time while using CCS 6:

Invalid project path: Include path not found (C:\Users\CrossLink2\Desktop\CCS Workspace\ExigentAlarms).

Invalid project path: Include path not found (C:\Users\John\Desktop\CCS Workspace\ExigentAlarms). 

Invalid project path: Include path not found (C:\Users\John\Google Drive\Exigent\Software Backups\CCS Workspace\ExigentAlarms\include). 

It is correct that this path does not exist on this PC, but I cannot find where I can remove this path in CCS. This path is not set anywhere in properties-> MSP430 Compiler, Inlcude Options, MSP430 Linker, or File Search Path. Where is CCS finding this include path setting?

My project is stored on Google Drive, which is shared between multiple PCs in multiple locations. The warning paths change based on which PC I'm using; but I can't find where to just eliminate these paths.

Everything compiles and works fine in my project, it's just annoying always getting this error. Thanks for any suggestions -

Chad C.

  • TI__Guru**** 173310 points

    Chad Christensen said:
    It is correct that this path does not exist on this PC, but I cannot find where I can remove this path in CCS. This path is not set anywhere in properties-> MSP430 Compiler, Inlcude Options, MSP430 Linker, or File Search Path. Where is CCS finding this include path setting?

    Can you attach a screenshot of your Project Properties->Build->Compiler->Include Options? There may be paths there relative to a build variable, rather than hard-coded paths, that may be triggering the error.

    The other possibility is that the path has been preserved in the project file from an older setting and not got properly updated/deleted. Please check this related thread to see if it helps.