• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 4084 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

System macro ProjDirPath defined incorrectly

jamp
Intellectual 520 points

My colleague just installed CCS4 but none of the projects build with his installation.  I noticed that the system variable ProjDirPath  was defined incorrectly. How does this get defined in the first place so that we can correct it?  The project was imported and everything works correctly on my machine.  We each define a custom macro for our top directory from which all succeeding directories are identical.  This macro is defined in window->preferences->General->Workspace->linked resources and is correctly used. But the ProjDirPath points to the wrong directory.  There are several other users and we can all build this project fine so there's nothing wrong with the project, the problem must lie in the setup or import of the project or the CCS installation.  Any ideas?

 

  • 0
    TI__Genius 15190 points

    It is an automatically defined internal variable. i.e. CCS/eclipse automatically configure it to project path. It is not user changeable/adjustable. Could you describe the issue that you are having with building?

    Thanks,
    martin

     

  • 0 in reply to MartinS
    Intellectual 520 points

    Since the path for ProjDirPath is incorrect and many paths are based on this, the compiler cannot find the include files it needs to build the project. I  understand it is a system variable that cannot be changed but it gets set somehow so how is it done in the first place. How does the "system" know what to set it to?

  • 0 in reply to jamp
    TI__Genius 15190 points

    It sets it to location of project files (i.e. .project .cdtbuild). Did you by any chance have  "Copy projects into workspace" option enabled? This would physically copy project files into a different location,. thus adjusting its path. However, if your project files are part of a larger source tree that remains in its original location, then that could be one of the reasons whey macro might appear to be invalid.

    martin

     

  • 0 in reply to MartinS
    Intellectual 520 points

    Where would I find the "copy projects into workspace" option?

  • 0 in reply to jamp
    TI__Genius 15190 points

    Project -> Import existing CCS/CCE Eclipse Project ; it is near the bottom of the dialog that pops up. 

     

    martin

     

  • 0 in reply to MartinS
    Intellectual 520 points

    That looks like it was the problem.  Thanks!!!