CCSTUDIO: Local Project Directory

Hello,

To add to this I'm working within the C2000ware motor control code.  I've not used CCS is some time and when I imported the project it created a local project file structure in my workspace but it didn't port the files into my workspace.  They are still sitting in the C2000ware directory.  I now need to create a separate branch fo this project so I can being to work with another engineer to add features to the code but without local files I'm uncertain of how to do this cleanly.  Really would like all files that aren't a compiled library to be local.

Thanks - Bruce

When you add files to a project you can choose to copy them into a project instead of linking them. If you're using one of our MotorControl SDK projects as a starting point, before you import it, you can find the example's .projectspec file and edit it (after making a back up) to copy instead of link.

You'll see a lot of lines in the projectspec that look like:

<file action="link" path="...whatever source file..." targetDirectory="...whatever directory..." />

By changing "link" to "copy" for all the source files (I recommend leaving the libraries to "link"), CCS will make local copies in your project when you import it. We don't normally have "file action" lines for all the #include paths though. If you want copies of those too, you'll need to add them yourself.

Whitney

Whitney,

Thanks.  That helps make things clear and I now see what I need to do with a new import of a proejct.  I guess the question now is whether there is an easy way to correct a linked project that's already been thru some level of modification.  Do I re-import it to as a new project but this time with the  modification above?

I don't know of any clever way to get CCS to convert links to copies in an existing project unfortunately. I think you would just need to remove the links and copy the files back into the project manually.

You maybe could experiment with the CCS Export functionality as well. I experiementally exported a project with linked files using the General -> File System export and by checking the "Resolve and export linked resources" I got it to generate a new CCS project with all of the linked files copied into it. When I imported the new project I still needed to delete the links to the SDK files, but since the files were also copied into the project, deleting the links allowed the CCS to find the local copies instead. This still doesn't help with the include files though.

What I was saying in my previous message is that if you're using an SDK example as a starting point, you can edit that example's .projectspec file as described and then reimport it. This time when CCS creates the project according to the projectspec, it will copy those files into the project workspace. As long as you haven't made a bunch of changes to customize the project already, this is probably the easiest option.

Whitney