Hi,
For Code Composer 4.0, what files are necessary to correctly capture a build configuration into source control (e.g., subversion)?
In the past (read: CCS 3.3), our company has been able to put a project directory, the source files, a .pjt file (code composer 3.3's "makefile"), the BIOS .tcf configuration and any miscellaneous linker .cmd files into accountability such that another engineer can do a "clean pull" of the repository and reproduce the associated library/executable as long as the same components (CGT's and BIOS) were used.
It's not clear to me how to accomplish the same thing with the CCS V4 IDE / Tool. There are several dot files in the project area, but it appears that the Eclipse front-end is managing a makefile in each of the target configuration directories (e.g., debug/makefile vs. release/makefile). I assume these are necessary to put into accountability, or are the auto-generated at build time? Can anyone provide some guidance or point me to a fine manual to read on this topic? What do I need to "check in" to ensure that someone can reproduce (or at a minimum identify) a build configuration?
Thanks!
