CCS v5.2.0.00069 : Path Variable / Include Options not working properly

Hi Daniel,

check your library include paths under

Build->TMS470 Linker->File Search Path

Unresolved symbol errors like this tend to come from the linker.

Please keep us informed.

Best Regards,

Lisa

Hi Lisa,

I have only two default paths at that location.

"${CG_TOOL_ROOT}/lib"
"${CG_TOOL_ROOT}/include"

Hi Daniel,

ok, sorry I think I misread the error you are getting. 

Were you able to use this build variable in previous versions?  Is this only the one project?  Have you tried a fresh project/workspace?  Is this an imported project?

Could you send screen shots and make sure no spaces or special/accented characters are used in the paths.  Also try a shorter path lenght, there is a max that CCS can handle but I do not necessarily suspect this might be what's going on here.

Best Regards,
Lisa

This method with variables is what my group uses with all our projects.  This specific project was working on another machine.  The project files were zipped up and sent to me.  I extracted and imported the projects as is.  However, now they are broken, with the error I posted originally.

So I just tried to re-import the project fresh, from the original zip file.  I noticed that the Path Variable  was incomplete/incorrect.  When I corrected the Path Variable, I received a new error. 

Could not write to file: C:\<project path>\.project.

Hi Daniel,

what version was the project created with? How was it imported-exported?

What is the project path in this case ... something that also needs correction or has spaces or special/accented characters?

Best Regards,
Lisa

The project was originally created with v5.1 I think.

It was "exported" by zipping up the source files.  It was imported using the "import existing eclipse project' method.

With the fresh import, the path variable was simply incomplete.  It got truncated to "${PROJECT_LOC}\.."

I made the "unable to write" error go away by going to the file properties and checking/un-checking the "read only" option.  However, the original error still persists.

Hi Daniel,

I would try either exporting the project using a proper export method..  Or instead of importing, bring the source and header files you need into the project manually.

Please give either of these a try.

Best Regards,

Lisa

The person who sent me the project (working on his machine) is running v5.2 also, same as me.

Even if I import only the files I need, the path variable error is still an issue.

Hi Daniel,

ook, let me get another pair of eyes here as well.  Any details would be helpful.
Best Regards

Lisa

To provide some more detail, it is as if the project is not refreshing, even though the path variable is updating.

When I check the path variable manually in properties, CCS is able to resolve the location correctly.  However, when I try to compile, I get the warnings.  This makes me believe the problem is somewhere in the build include process.

I am also able to link files to my project using the path variable without issue.  

I have also checked Build->Variables tab and did not see anything that would conflict in terms of variable names.

As I mentioned in my last post, the build variable in question does not exist.  I am looking in Properties->Build->Variables, with "Show system variables" checked.

So the problem was my lack of a Build Variable.  I declared a new build variable with the name I wanted and that resolved the issue.

Why did the build variable disappear from the project when it was copied to my machine?  I also checked the other computer and it existed there.

Thank you both for your help.

Hi Daniel,

glad it got sorted and all the best.   Include paths and variables are a known problem when porting projects unfortunately ...

Best Regards,
Lisa