LAUNCHXL-CC26X2R1: Hidden files within SDK needed to compile code?

MT2650

Hello,

I'm trying to store the Simplelink SDK (version 3.10.01.11) into our configuration management tool (ClearCase), but am running into issues with adding some of the files. When copying the SDK over, a bunch of hidden files were also copied over. (.vers_b200, .vers_g200, .vers_r200, .xdc-F09, and various others) These files are empty (0 bytes), and ClearCase doesn't allow empty files to be added to source control. These files are scattered throughout the kernel directory and the xdctools directory. Are these files needed to compile the code properly? Can I delete them without any negative side effects?

Thanks.

over 7 years ago

0 IUsedToBeARealPerson (M-W) over 7 years ago

TI__Guru 58425 points

Hi MT,

I'm not able to give you any clear answers to this, my advice would be to "try it" and see if it works if you check it out on another computer. As the kernel build process is rather complex, it is quite hard to get a full overview of which files exactly is required to build (tho I would expect these hidden files to be some kind of generated output).

0 MT2650 over 7 years ago in reply to IUsedToBeARealPerson (M-W)

Intellectual 400 points

I understand, thanks. Tried having another developer build the code and it compiled successfully, so seems like they aren't needed, or are generated output as you mention.

Thanks!

Bluetooth®︎

Bluetooth forum

LAUNCHXL-CC26X2R1: Hidden files within SDK needed to compile code?