Manage version source code in CCS automatically

Long Pham Tan

Other Parts Discussed in Thread: UNIFLASH

Hi,

I am finding the solution for generating a header file that defines the version number for my project in CCS by writing a custom script in pre-build step.

I have seen the link https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/625939/ccs-ccstudio-version-management. But there is no detail guide , can you give me the detail guideline for this solution.

Thanks,

Longpt

over 3 years ago

0 JohnS over 3 years ago

TI__Guru**** 162895 points

Longpt,

The details of this would be dependent on your specific environment. They general flow is typically something like this:

version.h present in the project
version.h has a #define with the version number
you have a script that reads the version number of your build from somewhere (usually a source control system)
the script writes that version into the version.h file
you setup a pre-build step in your project that calls the script

You can setup the pre-build step in the project properties here:

Regards,

John

0 Long Pham Tan over 3 years ago in reply to JohnS

Intellectual 391 points

John,

Thanks for reply. I am using CCS on Window 10. Can you guide me how to write script file?

Thanks,

Longpt10

0 JohnS over 3 years ago in reply to Long Pham Tan

TI__Guru**** 162895 points

Longpt10,

I am not going to be able to assist you with that.

Regards,

John

0 Kier over 3 years ago in reply to Long Pham Tan

Mastermind 9470 points

As JohnS hints writing a script is too wide a topic to answer here. You can use any external script tool called from pre-build steps to update your version.h. e.g. PERL, Python and so on. I have used sed.exe in the cygwin tools folder of CCS to modify my version file. This way the script tool is always available to a CCS user. You can see an example in this post:

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1087105/can-javascript-know-the-project-source-location/4028805?tisearch=e2e-sitesearch&keymatch=build_info.h#4028805

My only other advice is that you should place your version number/string at a fixed address. That way, when somebody asks "what version of software was used for this test?" you always have the fallback of reading the fixed address using UniFlash or debugger.

+1 Long Pham Tan over 3 years ago in reply to Kier

Intellectual 391 points

Thanks for your advice!

Code Composer Studio™︎

Code Composer Studio forum

Manage version source code in CCS automatically