• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1950 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS: Version control and using jenkins with Simplelink CCS projects?

AnBer
Mastermind 29705 points

Tool/software: Code Composer Studio

Team,

I have found some good inputs regarding version control for CCS 5.x projects in the below thread:
https://e2e.ti.com/support/development_tools/code_composer_studio/int-code_composer_studio/f/90/t/471876?tisearch=e2e-sitesearch&keymatch=CCS%20IDE%20version%20control
I guess it is still valid for CCv6 and CCSv7.

-Do we have any tips or guidelines in using Jenkins for building CCS projects?
Is there a tutorial like to use Jenkins for managing CCS projects?
I have not find much relevant info on the E2E yet.

Thanks in advance,

Anthony

  • 0
    TI__Guru**** 450031 points
    Hi Anthony,
    I don't have much experience with this myself and I'm not aware of any CCS specific documentation (though there is some Jenkins+Eclipse information out there on the web). I'll see if there might be something internal.

    Hopefully others who do have experience can chime in.

    Thanks
    ki

    I di
  • 0 in reply to Ki
    TI__Mastermind 29705 points

    Hi Ki,

    I just realized that the above post about version control is available externally. So I copied some part of it below:

    >>>>We use an CCS5.x IDE for day to day development, but would like to make use of version control.

    What processes are available to us to achieve this?

     

    The main difficulty is the project is stored in our CVS system, and then the IDE dynamically creates the make files and the builds from those. Projects are relocatable. They can be moved from one point in the filing system to another moved to another PC. The makefiles are not relocatable. Putting these in the change management system would fail unless ever PC was configured the same and only one version of the software existed on the PC at once.

     

    One solution we have used is to take the makefile, edit them so they are relocatable, and then build from them.

    This has the issue that now changes made in the IDE are not propagated to the make files. Some changes are very important, such as optimization settings.

     

    The second solution is to create a script that runs the IDE in a headless mode and creates a workspace, imports the project and then builds the software though the IDE.

    This is very time consuming and requires a full set of tools and licenses for the build machines.

     

    A particular issue is the use of the tool that processes the TCF file. (xdctools/tconf?)

     

    >>>>The makefiles are not meant to be checked into version control. They are generated files from the project manager and not meant to be modified (assuming CCS managed make projects are being used). Only the project metadata files are needed.

    More details: http://processors.wiki.ti.com/index.php/Source_control_with_CCS