• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 3415 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.

How to export full workspace?

Ludwig Schlegel
Intellectual 445 points
Other Parts Discussed in Thread: CONTROLSUITE

 Hello,

I use CCS  Version: 5.3.0.00090 and a Concerto microcontroller. I have a workspace including 2 "library projects", one project for ARM M3 and one project with code for the C2000. I use customized target configuration and gel files. Also I use some includes from controlSUITE.

Now I wanted to give all this to a college, that he can help me developing c-code. But we didn´t find a possibility to export all includes and customizations I did. 

I only found in the wiki something about portable projects and shared projects. But this is just for one project! Exists there the possibility to export the hole workspace ??? This would help allot!! 

 

 

 

  • 0
    TI__Guru*** 130875 points

    Hi Ludwig,

    there is no easy "catch all".   However there are a few things you can do try.

    What I would recommend

    ->share projects separately as per our wiki topics

    ->share all available workspace settings by

    1. Completely setup your workspace.
    2. Export the preferences of the workspace to file. Select File -> Export -> Preferences. Then select “Export All” and set the output filename. Click Finish.
    3. Now to load your preferences, open the workspace that you want to apply the preferences to. Then select File -> Import -> Preferences. Select the preferences file and click Finish.

    Note not every since preference setting is exported but most and hopefully what you need will be there.    Unfortunately these are pretty much you only options.  Do you use source control at all?  Another thought might be to put the workspace in a shared folder accessable to all required developers.

    Hope this helps.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 445 points

     Hi Lisa, 

    it´s a bit strange and funny, but there is no page about shared projects anymore. I found it last week at the end of the CCS5 page (http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5). There was something written about a bug in the actual ccs version. I couldn´t reproduce this bug but anyway, the instructions out of the wiki page didn´t work. Where is the wiki page? Or how to share projects?

    And about your second point "exporting workspace settings". There is only the possibility to export Key Preferences, Editor Appearance and Behavior. It´s nice to have the possibility to export them, but I want to export much more. 

    At our company we use Bazaar for source control. Usually we only have c-code in our repositories to keep them small. The ".metadata" folder with all the workspace settings is quite big (22 MB) and there are over 1500 files. I need do know that of this files are important and what I can leave. Exists there a list with important files?

    And even if I include the .metadata folder in my repository, I will still have problems with external includes. Is there something on the road map of CCS development to get this easy "catch all" functionality??

    Best Regards,
    Ludwig

  • 0 in reply to Ludwig Schlegel
    Mastermind 6240 points

    Hi,

    Not answering your questions, but trying to help a bit... this presentation (http://downloads.ti.com/dsps/dsps_public_sw/sdo_ccstudio/workshops/CCSv5/CCSv5_AdvancedWorkshop.pdf) has some examples, in slide 83 you have the information about which files shoud be checked. The section about sharing projects start in slide 62.

    The link came from here.

    Regards

  • 0 in reply to Johannes
    TI__Guru*** 130875 points

    Hi Ludwig,

    this is the wiki I just verified on project sharing.  Unfortunately what you are looking for is actually eclipse functionality and therefore dependant on their open source community and not us.

    http://processors.wiki.ti.com/index.php/Portable_Projects

    I would simply do a google search ... these two results for example explain why sharing a workspace is not recommended and some ideas around workspace and settings sharing.  Workspaces are intended to set the individual environment.

    http://stackoverflow.com/questions/8445522/sharing-a-workspace-for-many-developers-in-eclipse

    http://stackoverflow.com/questions/2078476/how-to-share-eclipse-configuration-over-different-workspaces

    Best Regards,

    Lisa