• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 1504 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/CC1310: Working on two PC with SVN

Noge
Intellectual 755 points
Part Number: CC1310


Tool/software: Code Composer Studio

Hi All,

I still have may problems when using CCS on a Work station and on a Laptop also together with SVN. If the Project being compiled fine on e.g. the workstation, then export it to an archive, and import it to the Laptop, the project won't work again and vice versa. Also using SVN Check in at e.g. work station and check out at the laptop usually won't work. Are there some best practise advices how to manage this?

Thanks.

Noge

  • 0
    TI__Guru**** 173310 points

    Noge,

    Here are a couple more references in addition to the one posted by Yikai. 

    Using Git with CCS (you mentioned SVN but concepts should be the same).

    Best Practices

    If you require further assistance beyond these references please provide us with specifics about the issues/errors you see when exporting/importing from archive. 

  • 0 in reply to YiKai Chen
    Genius 4455 points
    We use SVN to manage our CCS projects and it works correctly.

    It seems like the reason you are having problems is because the project is not setup properly for (1) version control AND (2) portability between workstations.

    YiKai Chen recommended the following link, which I also recommend, but this only handles item 1 above: processors.wiki.ti.com/.../Source_control_with_CCS

    In addition to that, to handle item 2, I recommend looking at Portable Projects with CCS here: processors.wiki.ti.com/.../Portable_Projects

    The information for CCSv6 is still relevant to CCSv7 and CCSv8.

    Setting up the project for portability means it will work correctly even if the project is checked out into different directories on the different workstations. For example in one workstation you might be working in drive C: and in another workstation you might be working on drive D:, but portability ensures it works anyway.

    In addition to the above, I have the following recommendations:

    Make sure that the version of CCS and compiler tools installed matches across all workstations.

    Make sure the TI software frameworks (e.g., TivaWare, TI-RTOS, etc) are all installed in consistent locations across all workstations -- best to install under C:\ti which is the default.

    Also, I am not using the Eclipse SVN plugin. Instead, I use TortoiseSVN and the command line SVN client that come bundled with and can (optionally) be installed with TortoiseSVN. This combination works very well and allows version-controlling of files that are not part of CCS projects, e.g., spreadsheets, schematics, PCBs, documentation, artwork, etc.

    Some notes about Subversion:

    You can have multiple Subversion clients on your computer (e.g., an Eclipse plugin, TortoiseSVN, command line tools, etc.) but if you want to use them interchangeably with the same working copies (e.g., perform some operations via the GUI, then drop to the command line for some special manipulations), then all Subversion clients involved have to be using the same version of the underlying Subversion library. Installing TortoiseSVN with its bundled command line tools (check the box for this during TortoiseSVN installation) ensures that you have both a GUI and a Command Line interface to the exact same version of Subversion.

    TortoiseSVN integrates directly with Windows Explorer to make managing and versioning files very easy, and (in my opinion) eliminates the need for any other IDE plugins, etc. AartiG mentioned Git -- there are similar "Tortoise" family clients (developed by different individuals but sharing some common pieces such as the icon overlay library) for Git, Mercurial, CVS, and others. (I don't recommend CVS. It's too old, unmaintained, and superseded by both Subversion and Git.)
  • 0 in reply to twelve12pm
    Intellectual 755 points
    Dear twelve12pm,
    thank you for your notes. I will check the installations an probably reinstall CCS. We also use TortoiseSVN. so I think the first it will work.
    BR noge