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: CCS/LAUNCHXL-CC2640R2: Error linking files from SimpleLink SDK across multiple PCs

Part Number: LAUNCHXL-CC2640R2

Tool/software: Code Composer Studio

Hi - I'm trying to develop on two different PCs, out of necessity because another engineer occasionally helps on a different PC from mine. I installed CCS locally then installed the SimpleLink SDK locally on both PCs. I have my workspace set to a directory in a Dropbox folder. We'll use Git(Hub) further down the line too but we need to get around this issue regardless.

I can import and build an example project from Resource Explorer on machine 1 but then when I go to build it on machine 2, I get the following error:

error #10008-D: cannot find file "C:\Users\me\Dropbox\Workspace\tirtos_builds_CC2640R2_LAUNCHXL_release_ccs\Debug\configPkg\package\cfg\release_pem3.oem3"

error #10008-D: cannot find file "C:\Users\me\Dropbox\Workspace\tirtos_builds_CC2640R2_LAUNCHXL_release_ccs\src\sysbios\rom_sysbios.aem3"

The other PC on which I first imported the project is named "pjb" so the full path is slightly different. Of course I could hackily fix this by creating a new user on PC2 that matched the username on PC1 but that doesn't seem necessary.

I've checked every single Properties, Build Settings, Configuration, etc. path that I can find and they all point to that particular machine's correct path, so I can't figure out why somewhere in there, the path from PC1 is being pulled in when I try to build on PC2. Can anyone help?

I'm only using an example at the moment because I built some real code off of one of the example projects and that doesn't work either, so I thought I'd re-start with the basics, but the basics won't cooperate either! 

Thanks!

  • Hi Phil,
    The Eclipse workspace itself is not designed to be shared that way. The metadata data stored inside the workspace folder likely has absolute paths that will prevent such sharing of a workspace cleanly. Each user should be using their own separate workspace. The project can certainly be version controlled and shared but I would recommend against trying to do this with the workspace.

    Thanks
    ki
  • Ah, okay. Thank you, Ki. That gets me a huge step toward my answer. I'll consider it resolved but it also opens up the question of where to find best practices for managing a team-oriented development project. Does this do the trick: Does this one apply equally to CCS7? processors.wiki.ti.com/.../Source_control_with_CCS
  • Yes, that article also applies to v7.

    Thanks
    ki