• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1004 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 v5 static library disassembly

Ga Ku
Prodigy 70 points

Hello,

I have two projects in CCSv5. One is supposed to produce a a static library which is used in another (just by copy pasting .lib file). But I do not  wish disassembly of the library code to appear in second project . Which option enables me to disable assembly generation? Obviously I am looking for some option which I can use in my library project and thus make the project not generate assembly in any other project it is used in.

  • 0
    TI__Guru**** 480331 points

    The compiler option to enable keeping generated assembly files is -k or --keep_asm. This option is usually not enabled by default. If it is on for you, you can turn it off by unchecking the option in the project properties under 'Build -> <ISA> Compiler -> Assembler Options'

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 70 points

    Thanks Ki.

    But this is not the solution.  --keep_asm is  not checked any ways. I am not talking about generating assembly file generation. I don't want any assembly to be produced even in the disassembly window in Debug perspective. It should show something like 'Source code not found'. Because I don't want to expose any code I used to build the library.

  • 0 in reply to Ga Ku
    TI__Guru**** 480331 points

    The disassembly view can figure out the assembly instruction from opcodes. That is the role of the disasembly view. It is not correlating any source code to the opcode so there would not be any 'source code not found' message. It is not showing the actual assembly source code that was assembled but just the assembly instructions that was translated by the debugger from the opcodes.

    Thanks

    ki