• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 551 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.

Default repository

Peter Steinberg
Expert 1640 points

I'm using CCS4.2.x

I've created my own SYS/BIOS RTSC platform (hardware repository).

Every time I create a project I have to manually add the path to the repository on the "New CCS Project" "Products and Repositories" tab.

How do I get CCS to add this path by default?

I've added the path in the preferences page (WINdows, Preferences, CCS, RTSC, Products and Repositories) but that has no effect.

 

Thanks,

  Peter Steinberg

  • 0
    TI__Expert 3550 points

    Hi Peter,

    peter steinberg said:
    Every time I create a project I have to manually add the path to the repository on the "New CCS Project" "Products and Repositories" tab.

     

    Currently there is no other way to add the repository but I agree it will be a nice feature to inherit from the global options.

    If you are creating a new platform  you can check the "Add Repository to Project Package Path" checkbox in the first page of the platform wizard. This will bring-up a dialog with all the projects in your workspace. Select the RTSC project to which you want to add the repository. 

     

    Regards

    Amit

     

    e 

  • 0 in reply to AmitMookerjee
    Expert 1640 points

    I need to share the repository among all the other engineers on the project.

     

    I'm finding that this version version of Code Composer makes it very hard for multiple developers to work on the same project.

  • 0 in reply to Peter Steinberg
    TI__Expert 3550 points

    Peter,

    To enable sharing of your repository, I would suggest creating a RTSC configuration project - which contains a configuration script (*.cfg) and all the RTSC properties like package path, target, platform etc. The application project  containing your C sources can then refer to the configuration project in order to consume RTSC content. In this scheme you just define one RTSC configuration project that can be reused by multiple application projects. This  also addresses your original problem of specifying a repository for every new application project.

    If the repository is located on a shared network drive, then all you need to do is export this RTSC configuration project and send it to other developers in your team (or check it in source control where others can check it out).

     For an example look at the SYS/BIOS Task example with separate configuration (screenshot is shown below). 

     

     

     

    Let me know if this addresses your problem.

     

    Regards

    Amit

     

  • 0 in reply to AmitMookerjee
    Expert 1640 points

    I have done that.

     

    I then create a new static library project, and after going through the various screens I get to the RTSC Configuration Settings screen

    where I need to add the path to the repository to be able to select my RTSC platform, hence the original posting.