• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 758 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: CC2640R2F: SVN integration of new "projectspec" projects

Harald Ilg
Genius 3060 points
Other Parts Discussed in Thread: CC2640

Tool/software: Code Composer Studio

Hy,

after working for some years with BLE Stack 2.0 and CC2640 we switch to BLE Stack 2.20 and CC2640R2. One thing that seems to be different is the organization of sample projects: I am used to projects that are described in ".procject" and ".cproject" files, in the new stack I find "projectspec" files.

One major difference seems the "Copy to workspace" option: In the old fashion, I never checked this option, the project files stayed at the original folder and all source files were integrated as "linked file" but also remained in their original place. So I simply added the whole c:\ti\ folder to svn and had the full control over my sources. In this way, the standard work flow (commit, branch, merge etc) worked as expected.

With the new procedure, whenever I import a project into CCS, a copy of all files is created into my workspace. When I do changes, I change the copies, no effect on the original files.

So:

- what is the recommended way of treating "projectspec" based projects with svn? This document only covers classic .ccsproject / .cproject / .project projects

- Is there a way of converting from projectspec to classic project organization?

Any help appreciated

Harald

P.S. I asked the same question in my post at BLE forum, they pointed me to this CCS forum

  • 0
    TI__Guru**** 173310 points

    Harald,

    Harald Ilg said:
    With the new procedure, whenever I import a project into CCS, a copy of all files is created into my workspace. When I do changes, I change the copies, no effect on the original files.

    That is correct, and is the intention of projectspecs. Most users actually prefer that the projects be copied into workspace rather than leaving them in the original location so they can make changes to source files without the worry of modifying the original that came with SDK. Unless the SDK is put into version control right away, making changes to original SDK source files is not ideal for most users. 

    With the projectspecs, when you import the example projects into CCS, the .ccsproject / .cproject / .project files will be generated for you. You can make the necessary changes to the project and then add the source files and .*project files into version control, like you would with any other project.

    Some additional information on this topic is in this page. It talks about Git with CCS but many of the general concepts should be relevant for other version control software as well.

    Hope this helps.