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

CCSv4: Organizing Target Configurations

Andreas Zoufal
Intellectual 305 points

Hello,

On the way of porting CCS3.3 projects to CCSv4. I had my first successful debug session now, great! Board is a custom borad using DM468, and emulator is Spectrum Digital XDS510USB.

As I see, the handling for Target Configurations is a little bit different to the previous CCS's? For CCS3.3 every developer did the configuration once for his local PC and uses it for many projects. The target configuration is stored on a central installation place, isn't it? And there is no sharing using SVN repositories.

For CCSv4 it seems the target configuration must be stored within the project tree for every executable-project, is this true? Is there any way to store the configuration(s) on a central place and use it with several projects to reduce duplicity? Can I link a target configuration into the project?

And does it make sense to share a target configuration in the SVN repository, is it relative to the other files (GEL, for example)? Can users using the same board types and the same emulator share this configurations?

So, I'm looking for the best practises in creating and using target configurations, GEL files, etc. I want to supply the developers with predefind configurations for easy use, if possible.

Kind regards,
Andi

  • 0
    TI__Guru**** 162305 points

    Andi,

    There are pros and cons of storing your target configuration in your project.  Being able to source control it is one upside, assuming the relative paths for each user work out.  You can inspect the paths used by clicking on the source tab at the bottom when you have a target configuration file open. 

    If you are using the same project on many targets then if you are storing target configs in your project you need to mark the one you want to use as active.  If I had a lot of projects using the same config then I probably wouldn't store it in the project.

    When creating a target configuration from the project view by default it will try to store it in your project directory, however you can check the box and it will save it in a shared location.  By default this is a folder under your user directory, but you can change it to whatever you want.

    If a project does not contain a target configuration it will use your "default" configuration.  You can open the target configuration view from the view menu.  This will show you all the target configurations you have in your various projects as well as those in the shared location.  You can then right click on one and make it the default configuration.

    Regards,

    John

     

    Regards,

    John

  • 0 in reply to JohnS
    TI__Genius 15610 points

    Andi, 

    Another option is to create a "dummy" project and store your target configurations in that project. You could select something like New->Project ->Other->General -> Project. You could then source control your target configs. You could link target configurations to your individual projects or not have a target configuration at all in the project and use the default setting as John described. 

    Martin

  • 0 in reply to MartinS
    Intellectual 305 points

    Hello,

    thanks for your input. My current solution is to create a new target config as usual, move it to a central position in the repository and correct the relative pathes with an editor. Then I link the file into the project. Looks good, seems to work, but I need to cross-check from a different computer.

    Kind regards,
    Andi