[quote user="Mike Fontes"]The reason I have brought this up is that providing the links as you do is fodder for destruction of the library sources. [/quote]
The controlSUITE examples do not come from the CCS team. However, that type of example (using references to source files instead of actually adding it to the project) is a common one which helps with project portability. The issue is that many source files are shared among various example projects and library projects. I tend to just back up the source files. It's something that I have always done in CCS and when using other environments.
[quote user="Mike Fontes"]I think there should be at least a visual cue to show which files are unique and which are libs.[/quote]
Linked files are identified by the little icon of a 'chain link' (or is it an arrow?) in the lower right corner of the icon of the source file.
[quote user="Mike Fontes"]I think there should be at least a visual cue to show which files are unique and which are libs. Better yet would be a copy option that was named correctly, which actually copied all the sources to the workspace folder so there would not be the chance of ruining the distribution code. The Copy all files button now does not copy anything but the one or two c files from the Controlsuite example, and leaves links that allow changes to all the lib files. That is a poor way to handle the file system. It is very bad when the user figures it out after loading and changing multiple files in multiple projects, and then finds that they are all broken![/quote]
Eclipse/CDT sees files that are linked and files that are physically in the folder as two different things. Files physically in the folder are source files that have been added to the project. Linked files are just that - the project only keeps a reference to the file. So the reference is part of the project, not the file itself. Now I admit that to the user, they will not care if a file is physically inside the folder or if there is just a reference - both are to be compiled and resulting object files to be linked by the linker. But CCS is leveraging Eclipse/CDT and this is what was inherited. Your suggestion certainly makes more sense and is worth investigating.