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

Can't copy files when importing project

Brian Peavey
Intellectual 410 points

  I'm running CCS Version: 6.1.0.00104 on Windows 7 64-bit, Service Pack 1.  I am trying to import several sample projects which I have downloaded to my PC and stored in C:\ti\simplelink\ble_cc26xx_2_01_00_44423\Projects\ble\SimpleBLEPeripheral\CC26xx.  I am trying to import these into my CCS workspace which is in a different directory.  To import these, I'm going to Project->Import CCS Projects.  I browse to the folder given above which contains the 2 projects I want (SimpleBLEPeripheral and SimpleBLEPeripheralStack), select the 2 projects, check the box that says "Copy projects into workspace", and hit Finish.  I am able to build the projects fine, but the source code was not copied into my workspace.  I've deleted the workspace, recreated it, made sure it is not read-only, but still unable to get the import projects process to actually copy the source code over.  When I look at the properties of one of the source files, it shows that it is a Linked file pointing back to the original source code location.

  How do I get the import process to actually copy the source files into my workspace?

  Thanks...

Brian

  • 0
    TI__Guru**** 463781 points

    Hi Brian,

    Most of the source files referenced by the BLE SDK projects are linked. This means that the project only keeps references to the source file in their original location, instead of having them physically part of the project. So the "copy project into workspace" would just copy the project itself with the references to the source files. This is by design since the BLE projects are dependent on the original source files being referenced from their original location.

    If you are interested in backing up the original source files, you can do the old fashion "copy the whole source tree" option. Another option is to export the project to create an archive of the linked source files.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 410 points

    Hi Ki,


      Thanks for the suggestion of exporting the project to get all of the source files.  That does work!  I now have a folder with the actual source code from the project.  However, if I edit one of the source files, it is still changing the source in the original location rather than the newly-created location.  So I still don't have a system where I can track changes to my project within a CCS project that I have created.  Is there an easy way to modify the project so that it actually uses the source within my tree rather than the sources back in c:/ti/simplelink/... ?

      Thanks...

    Brian

  • 0 in reply to Brian Peavey
    TI__Guru**** 463781 points

    All exporting the project did was archive the project and all source files for it (added or linked) to a zip. The actual project in your CCS workspace will still reference the originals.

    Besides using source control, if you want to work with copies instead of the original, you should make a copy of the entire source tree (don't use the export archive, but make a copy of the whole tree) and then modify the linked resource path variable 'ORIGINAL PROJECT ROOT' to point to the equivalent location in the copy:

    All the source files are linked with the ORG_PROJ_DIR variable which is dependent on ORIGINAL_PROJECT_ROOT. So if you update ORIGINAL_PROJECT_ROOT, then you should be good.

    Before you try this, I strongly suggest you get familiar with linked resource path variables and build variables by reading up on 'Portable Projects':

    Good luck!

    ki