Help with setting up Revision Control System
I'm using Perforce and trying to setup the depot such that all the files used for the project are in the depot.
Ideally, I would add the compiler but I've decided not to do that for now. But I would like to add the include files, target configuration files, libraries, etc. to the depot and point the compiler to use the copies in the depot rather than the CrossWorks directory installation structure.
Any suggestions on how to do this? I'm thinking of writing a batch file to copy these directories into the depot tree and modifying the macros ($(StudioDir), $(TargetsDir)) to point to the directories in the depot and then running the batch file whenever I update CrossWorks. Is that a good way to do it?
Thanks in advance for your help/suggestions.
-
I would like to use either RCS or CVS under Windows with Crossworks. I downloaded TortoiseCVS, but it looks like a client-only package, however, there are hints of being integrated into explorer. Is there an easy way of running CVS or RCS on Windows? At the moment I use the Mac OSX RCS or CVS and copy files between boxes, but it gets messy. I would also like to split out Kinetis projects for K60 K40 and within these devices for different boards. The main startup files are linked as Rowley ..-> CrossWorks .. -> packages -> targets -> Kinetis -> KiinetisStartup.s as an example on Windows and version 2.2. If I try to use my own copy, I get asked to reload the file and it prefers the original Rowley supplied file. I tried to add in other files and remove the original from the build. What do you folk do who work on multiple vendors' boards with an array of startup files?
Thanks.
Please sign in to leave a comment.
Comments
3 comments