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.

  • TI Thinks Resolved

CCS/CC2650STK: Copy exisiting BLE stack example without effecting old version CCS V8

Intellectual 870 points

Replies: 3

Views: 60

Part Number: CC2650STK

Tool/software: Code Composer Studio

Hi I wrote some months ago that I had the issuse to make a copy of exisiting project and making changes without affecting the old version of the project. I was used to do like the following link explained:  and it worked. I made a copy of the ble stack root folder and created a new workspace and everything was working. Now I wanted to do some updates on it again, so I did the same steps again and I realized that the changes are affecting the previous version as well. Why does it happen? -- I did not do any update on CCS so I am still using the same verison than 9 months ago.

Do you know how to solve this problem?

  • Guru 166720 points

    If there are common source files that are linked to both projects, then any changes made to those files will appear in both projects. More information on linked files is in this page: http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#adding-or-linking-source-files-to-project

    For example, if project1 is in directory c:\ble\project1 and project2 is in directory c:\ble\project2, and there are source files in c:\ble\source\common that are "linked" to both projects, then any change made to that source file will be reflected in both projects.

    To confirm whether the file you modified is a linked file, you can right-click on the file to go Properties and check if the Type is "Linked File".

    If this explains your observation and you wish to change the behavior, you have to ensure that all source files are added to the project rather than linked, as explained in the User's Guide referenced above.

    Hope this helps.

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Explore Code Composer Studio documentation and resources using online Resource Explorer
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

  • In reply to AartiG:

    Hi thank you soo much for the response. But why before it worked out like it is recommended in the stated link? It is as well for CCS v8?

    Thank you for your help. Even in a previous thread I was asking and I was told to do it like that look:  Check out the last thread of the post. What do you think?

    Thank you soo much

  • Guru 166720 points

    In reply to sensortag_fan:

    The procedure outlined in the wiki link you referenced in your first post and the recommendations in the other thread you referenced should still work for CCSv8. If it does not, then there is something going on with the variables and path similar to what was discussed in your other thread. Also as far as linked files, if the same file is linked to multiple projects, changing the file in one project will reflect in other projects as well. That is the nature of how linked files work.

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Explore Code Composer Studio documentation and resources using online Resource Explorer
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

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.