Forums

CCSv5 / Revision control tutorial

This question is answered

Posted by Tim Sloper

on Apr 16 2012 12:57 PM

Intellectual880 points

Support,

Do we have a tutorial for getting started with revision control in CCSv5?

Thanks,

Tim

All Replies

Posted by Lisa TI

on Apr 16 2012 13:04 PM

Guru99755 points

HI Tim,

let me assemble and send you some relevant material.

Cheers,

Lisa

Posted by Lisa TI

on Apr 16 2012 13:38 PM

Verified Answer

Verified by Lisa TI

Guru99755 points

Hi Tim,

Here some relevant available material. We do not specifically have a tutorial on version control but many of these topics are relevant and related.

http://processors.wiki.ti.com/index.php/Category:CCS_Training

http://processors.wiki.ti.com/index.php/Creating_portable_projects_in_CCSv5

http://processors.wiki.ti.com/index.php/Project_Sharing

http://processors.wiki.ti.com/index.php/Portable_Projects

http://processors.wiki.ti.com/index.php/CCSv5_Fundamentals_Workshop

http://processors.wiki.ti.com/index.php/CCSv5_Advanced_Workshop

http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

Please keep us informed if there is something further you require.

Best Regards,

LIsa

Posted by John Enright

on Feb 14 2013 10:57 AM

Prodigy50 points

Hi, I was hoping to resurrect this thread.

I'm having some trouble sharing projects through an RCS (we're using subversion). I'm trying to figure out what I'm missing.

We have the following setup (abstracted a bit):

I have the CCS project definition

\$(DEVELOPMENT_ROOT)\workspace\MY_PROJECT

and the source files

\$(DEVELOPMENT_ROOT)\MY_SRC

This local directory tree is under source control, but some individual files may not be.

Source control for the source files are not a problem. The only concern is the project itself.

So I can create a project that used linked resources, based on a local definition of DEVELOPMENT_ROOT. However this absolute path definition appears in both .project and .cproject files in the MY_PROJECT directory. So when I put the project under source, it's not really portable any more.

If Alice creates the project and puts these files under control, Bob can then check out the project. Bob can edit the definition of the DEVELOPMENT_ROOT variable, and build the project. But this changes the project definitions in .project and .cproject. and from a source-control perspective, this tree has now changed.

I do want the project settings and file list (linked resources) to be under source control. I do not want the variable definitions to be. Is there a way to do this?

Thanks for your help.

John