• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 1479 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.

The proper way to create portable CCS 5.1 projects?

ReinierC
Expert 2425 points

Hi,

Can someone please advise me what the proper way in CCS 5.1 is to create a portable project, i.e. create a project in CCS5.1 on one PC, check the relevant files into source control (such as CVS), check the project out on some other PC also running CCS 5.1, run some batch file to get all the dependencies (if applicable) of the project also from the source control database and automatically perform the necessary configuration steps. After this is done, the user should simply open CCS 5.1 and at this point the project(s) should already be in the workspace and the user would then simply be able to click on build to compile the entire process.

I'm sure there must be an easier way than exporting the project on one PC and then again importing it on the other PC? I came accross a Portable Projects link on the CCS5.1 wiki, but its too cryptic to really get an idea of what the recommended way of doing this is.

Your help would be greatly appreciated!

Regards

  Reinier

  • 0
    TI__Guru**** 474721 points

    Hello Reinier,

    There is a section on creating a portable project in some of the CCSv5 workshops. It walks you through how to do this. Check out slides 86 to 101 in:

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/workshops/CCSv5/C2000/CCSv5-Workshop%28C2000%29_2.pdf

    Hope this helps

    ki

  • 0 in reply to Ki
    Expert 2425 points

    Hi Ki-Soo,

    Thank you for your reply, the slides were indeed helpful. However, I just have another question: how do you automate workspace management? In our case we have multiple projects, and I believe it would be sensible to place each project in its own separate workspace. In other words, once I have installed CCS 5.1, I want to check out a project, which also checks out a batch file. When I run this batch file, it should in turn check out all the dependent projects as well as the actual source files. This batch file should then also automatically create a workspace for the project and import the project and its depedent projects into the workspace. When I then open CCS 5.1 I should be able to select which workspace I want to work in and once the workspace is loaded, simply hit the build button to compile everything from scratch.

    Based on the slides you provided, I think I should be able to create portable projects with only relative paths, but how do I automatically create the workspaces as I described above?

    Thanks in advance!

  • 0 in reply to ReinierC
    TI__Guru**** 474721 points

    Reinier Coetzer said:
    This batch file should then also automatically create a workspace for the project and import the project and its depedent projects into the workspace.

    You do not need to create a workspace folder separately. You can use the project import command to import an existing project into a workspace. If the workspace location does not exist, the command will create one first before importing.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2425 points

    Ki-Soo,

    Thank you for the link, it was most useful and I believe I now know how to create portable projects and automate the importing and building thereof.

    Just one note though, when importing a project that contains a number of dependent projects in the workspace, I get the following error: "assertion failed: Operation was not prepared". I believe this is a known issue in CCS 5.1.0 (see SDSCM00042818) and I'm currently busy downloading CCS 5.1.1, which I hope fixed this issue??

    Reinier

  • 0 in reply to ReinierC
    TI__Guru**** 474721 points

    Reinier,

    That bug is still under investigation hence it is not yet committed to a release. It will not be in 5.1.1. Sorry.

    ki

  • 0 in reply to Ki
    Expert 2425 points

    Ki,

    It appears as though the command line project importing now works in CCS 5.1.1, or I'm at least not getting the "assertion failed" error anymore (yet!). However, in CCS 5.1.1 itself, it still throws away the dependent projects in the dependencies tab from time to time.

    Reinier