• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 554 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.

Original question:

CCS headless build - passing preprocessor definitions

Question about build configurations and differences in .out file - MSP430FR2475

Samyukta Ramnath1
Intellectual 770 points

Hi! I have an MSP430 project for which I wanted to maintain two sets of builds (e.g. a 'developer' and a 'customer' build) based on different preprocessor directives. We are using Code composer studio to generate our builds. I created a new build configuration copied from the 'Debug' configuration, called 'Customer'. I simply built the new configuration, assuming that the build should be identical to the output files generated by the Debug configurations. This new configuration 'Customer' configuration generated a .out file of different size than the Debug configuration; however, the .txt file was the exact same size and was indeed identical between the Customer and Debug build configurations. The aim was to have 'Customer' build define a preprocessor directive that enabled some code to have the two builds. 

Why was there this difference in the .out file size? Is this expected? And why was the .txt file the exact same as generated by the two configurations?

  • 0
    TI__Guru**** 476051 points

    Hello,

    Samyukta Ramnath1 said:
    This new configuration 'Customer' configuration generated a .out file of different size than the Debug configuration; however, the .txt file was the exact same size and was indeed identical between the Customer and Debug build configurations.

    I assume the txt file you refer to is output from the Hex Conversion Utility. Note that the *.out file consists of both the program binary that is to be loaded to the MSP430, and the generate debug symbols loaded to the debugger for debug visibility. if the generated hex output is the same but the out file is different, it is likely that there are debug symbol differences. Remember that debug symbols have path information. The path between the two out files can be different because of the difference in name between the build configuration names. If the out file size difference is really big, then one could have been built with full debug symbols while the other has minimal symbols.

    Hope this helps

    ki