I have this associated issue -- I tried exporting a project with links to source files in the makefile to a different directory and building it there -- essentially trying to exporting a makefile. I have a project supported across multiple BF5XX and SHARC 21XXX and I did not want all the projects to be in one directory.
When I tried to build the exported project with links to source files -- it failed as all the links were relative. Unlike VDSP, there is no prompt to say for CCES -- tell me where you have hidden the files and I will adjust the links.
I have a student working on CCES plug-ins (teaching me how to build them :-) ). Sounds like this master list of makefiles might be useful in getting the app to change the relative links issue.
TerryXu -- This is not happening immediately, but if this App exported the makefile directories -- what would you want it to do then? I could see it popping up windows and then doing text substitutions. What else?
Craig -- I tried exporting a project and bringing it back to change from a SHARC to a Blackfin processor -- again a form of exporting a makefile. -- Could not do find an obvious way to do that from within CCES 1.0.2 -- any suggestions
Reason I needed this -- I had built two separate projects by hand -- identical in file content except for processor family. I manage to totally corrupt the makefile of one project. So I deleted it and tried to export the project as SHARC, rename it and bring it back to convert to Blackfin rather than trying to rewrite the project with all those relative links. As long as it was brought back to the same directory (around about way of exporting a makefile) I could change between variants of SHARC21XXX but not switch to Blackfin.
Also -- another reason for wanting to support a makefile is to refactor (break-up) a large project into a series of smaller projects all making libraries.
Thanks
Mike