• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 757 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.

CCS v3.3 : How to make project moveable from one location to another?

Robert Smith
Intellectual 640 points

I am using CCS v3.3 for DM642 based application. My workspace includes 4 projects.

My projects are located (for example) in C:\Path\To\MyApp folder. If I copy my projects to another location, let say, C:\New\Path\To\MyApp and try to open workspace from that location, CCS opens it OK. However when I try to rebuild my projects in new location CCS actually build projects in old location. CCS doesn't complain or display any errors, simply takes source files from old location and produce its output files in old location. Seems to me that CCS project definition file contains absolute path to project original location.

So I've opened MyApp.pjt file in notepad and I saw the following:

[Project Settings]
ProjectDir="C:\New\Path\To\MyApp\"
ProjectType=Executable
...

[Source Files]
Source="File1.c"
Source="File2.c"

...

So the pjt file contains absolute path to original project  location.

My question is how can I make projects moveable from one location to another, so I can build them in any location?

How can I prevent CCS from using absolute paths?

Thanks

  • 0
    TI__Guru**** 463941 points

    Hi Robert,

    Check out the below app note:

    http://www.ti.com/lit/an/spra913/spra913.pdf

    Even though it applies to CCSv2.2, it applies to v3 also.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 640 points

    Hi Ki,

    Thank you for your response. I however doubt that usage of macros can resolve described problem.

    Robert

  • 0 in reply to Robert Smith
    TI__Guru**** 463941 points

    Robert - you can use macros in your pjt file to eliminate the absolute paths. That was your main question in your original thread.

    FYI - ProjDir will always update to the current project directory (location of the pjt file). As you can see you example, it is pointing to you new directory.

    looks like your source files are relative to the pjt file so they look file. What I suspect is not are that you may have some absolute paths to where your object files and executable are generated. You can replace those absolute paths with a macro and update the macro to which path you wish (pick up old path or new) without needing to update the pjt anymore.