How to strip .debug section of a library in code warrior

[whizpb]

I have created a code warrior library project to generate a library as output. The library has .debug section which I would like to strip before using this library in any other project.

Is there an option available in the Code warrior IDE to strip the library of its .debug section?

[stanish · Accepted solution]

Hello Prashant,

You can disable debug information for specific file or entire group by removing a black dot icon (you can on/off debug info by double clicking on the symbol) in the debug column in the Project manager (see attached screenshot below).

This should work in all CodeWarriors based on Classic IDE.

Hope it helps.

Stan.

[whizpb]

Thanks Stanislav. This resolved my problem.

[trytohelp]

Hi.

Do you use CW for MCP55xx/56xx V2.10 or older version ?

Have a great day,
Pascal
Freescale Technical Support
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[whizpb]

Hi Pascal,

Yes, I am using MCP55xx/56xx v2.10 SE. Does it have a known limitation? Do any alternatives exist for it?

Prashant

[BlackNight]

You should be able to use the strip program for this:

https://sourceware.org/binutils/docs/binutils/strip.html

You find the program in

C:\Freescale\CW MCU v10.6\Cross_Tools\arm-none-eabi-gcc-4_7_3\bin

Erich

[whizpb]

Hi Erich

Thanks for your quick response. The CW installation you referred to is for ARM.

I am using a Power PC installation of the Code Warrior for MSP56xx and do not see a similar strip utility being available in the package.

Prashant

[BlackNight]

I'm not familiar with that tool chain, but I believe it is based on GNU, and therefore it should include that strip utility. But that strip utility is operating on standard .elf/dwarf files, so you should be even be able to use it from an ARM GNU toolchain.

Erich