• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 599 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/BLE-STACK: Version Control of BLE Stack related source files.

Martin Beisteiner
Prodigy 80 points
Part Number: BLE-STACK


Tool/software: Code Composer Studio

Hi everybody,

I have a question about version control of source code using the BLE Stack (BLE-STACK V2.2.1).

In TI's Getting Started Guide I found the hint "TI recommends that users start their development on a project starting with simple_, unless a specific function (such as heart rate, cycling sensor, and so forth) is required."

When I started investigating the structure of the source Code of the examples I noticed that all necessary files are inside the src Folder of the BLE Stack (ble_sdk_2_02_01_18\src). There are files which belong to one of the examples and there are also files which are used by all of the Projects. Until now I developed firmware for MSP430 projects without any operating system or source components like the BLE Stack an therefore all of the source files where under my control and easy to manage with svn. Now I am not sure how to handle the version control of all source file related to the BLE Stack and my own files.

Could you please give me some examples how you are managing version control of your projects which are using the BLE Stack?

Thanks for your help in advance!

 

  • 0
    TI__Guru** 105180 points
    Hello Martin,

    We use git internally here. You can install the SDK and create/add all files to the git repository. Note that if you intend to change any files in the TI-RTOS SDK (e.g., board files) then you should add that SDK to a git repo.

    Best wishes