Invalid project path

Matt McConnell said:

I believe I deleted these directories outside CCS, i.e. Window Explorer, early on.  The directories do not exist, and are not part of the project at this point. 

Although the directories are no longer part of the project, perhaps the project metadata files were not correctly updated to reflected that. You could try manually deleting references to this path in the .cproject file, as per this post. But be sure to make a backup copy of the .cproject file before editing it in case the suggestion does not help.

Could you please attach a screenshot of the error message as it appears in CCS? Also please zip up and attach all of the project metadata files (.cproject, .ccsproject and .project) so we can take a look at what may be generating this message.

When you reply to a post, click on "Use rich formatting". The pane that opens up will have icons for attaching images, files, etc.

EIT_FODR.zip

The project files look fine and provide no indication of why those messages are still appearing. They may just be lingering stale warnings, and if so you can simply select and delete them from the Problems view. Hopefully then they will not reappear on the next Build/Rebuild.

I deleted them in Problems window, but they reappear after every build? 

Matt McConnell said:

I deleted them in Problems window, but they reappear after every build? 

That is quite odd. One thing you could try is to clean the workspace or import your project into a new workspace: 
http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv6#General_IDE

If the issue is due to workspace corruption the above may help. If it does not help, then the project itself may be corrupted or there is something else going on, in which case the only way I can think of to get rid of the warnings would be to create a new project from scratch.

Sorry about the inconvenience.

I've been trying to reproduce this but have not been successful so far. Are you able to zip up and attach a project (along with detailed steps) that can be used to recreate this warning? If so, we could investigate it further.

I tried to repeat steps on a new simple project, but was unable to cause error.  I moved all files to this project, no errors. 

Is there a way to provide the project path to runtime support library option on the general tab?  I would like to locate all source files in project directory, vs. fixing it with path by browsing.

Matt McConnell said:

Is there a way to provide the project path to runtime support library option on the general tab?  I would like to locate all source files in project directory, vs. fixing it with path by browsing.

Yes, you can click on Browse next to the Runtime Support library under Project Properties->General, and browse to the library. Alternately, if you are locating the runtime library somewhere within the project directory, then it will be automatically picked up for the build. In this case, no explicit path specification is required.

Matt McConnell said:

Browse will not let me call out project root.

That is correct, 'Browse' will add it as a hard-coded path.
You could try linking the file directly to the project and set the linked path relative to the variable PROJECT_ROOT. Hope that helps!