• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 654 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/LAUNCHXL-CC2640R2: LAUNCHXL-CC2640R2: how to deselect 'Copy projects into workspace' in CCS7

Ji-won Lee
Genius 3630 points
Part Number: LAUNCHXL-CC2640R2

Tool/software: Code Composer Studio

Hi experts,

I would like to deselect the 'Copy projects into workspace' when importing an example project in CCS7.

When I was using BLE 2.2.1 SDK along with CCS6, I can do that, while it is selected automatically even though I did deselect it in CCS7.

Actually I want to manage some predefined symbols and else on git management, so, I don't want to use a separate workspace folder as it is not convenient.

Thanks in advance,

Ji-won Lee

  • 0
    TI__Guru**** 169754 points
    Ji-won,

    Several recent SDKs are designed in a way the project is created on-the-fly while importing it to the workspace - technically speaking, they are defined as a ProjectSpec:

    processors.wiki.ti.com/.../ProjectSpecs_in_CCS

    The advantages of ProjectSpecs offset the benefits of having separate projects for the maintainers of the SDKs. Also, historically the ability to leave the projects in their original places posed problems for a vast number of users that inadvertently broke their code only to see they couldn't go back to a previously working state.

    All this to tell that, unfortunately, the separate projects as provided by the BLE stack are not being emphasized anymore and risk becoming extinct.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    Intellectual 865 points

    I believe the problem is even greater than you describe because some of the files are linked and stay in the original location and some are copied, this happens no matter if you choose to click the copy or not (It is possible to press select all in which case it isn't clicked but it still copies to the workspace).

    For example PROFILES are linked and not copied so if you want to change an existing profile you have to do it in its original location. I guess this is why it says in CCS  wiki (Projects and Build Handbook for CCS)  that it is better to not copy.