segger studio: how to obtain a list of all files used in a project?

[Hugo Habicht]

Hi all,

in order to put the whole project under a decent version control system I need a list of all files used in the example project in segger studio.

The c source files, assembler files, libraries and hex softdevice can be easily extracted from the project file. But the header files seem to be available only by going through each individual source file which is no option.

So is there an efficient method to obtain a list (full path preferably without that ../../../../../ nonsense) of all files?

Kind Regards,

[Simon]

I assume you're working with the nRF5 SDK, not NCS.

This may help: https://stackoverflow.com/questions/15976080/list-of-all-header-files-included-by-a-c-file

However, another approach is to only include your project in the version control system repo. E.g. if you are working with the example ble_app_uart and you're using git as a version control system, then run git init inside <path_to_sdk>\examples\ble_peripheral\ble_app_uart.

If you have modified any of the defaults source or header files in the SDK, you have to include this in your repo as well. In this case, creating a patch of the whole SDK is useful. Then other people can simply download the appropriate SDK and apply the patch.

Best regards,

Simon

[Hugo Habicht]

Hi Simon,

running gcc over all files would be too time consuming particularly that I cannot generate a makefile (another post here).

I think running git inside the path would not work because it will miss a lot of files in the SDK 'components' directories a.s.o. I'm aware that you should not modify those but in order to replicate the whole system at a later stage I'll have to have all files under version control.

What I did in the mean time wrote a little REXX script that goes through the project file and all dependency files to collect all files including libraries, assembler, map elf and hex files. The ../../../ constructs (that are in my humble opinion a serious problem in Nordics directory structure) I could replace with a proper path using the project file directory.

I also copied all files into a single work directory because path names over 110 characters long are simply ridiculous. I deduct that most people in Nordic are slaves of the mouse :-)

Kind Regards,