0

I have four libraries that I wrote in C. Now I want to share these libraries (static libs for example, libA.a) with a software developer who will use them to generate a "final" executable.

My question is, how can I delete the debug symbols so that he doesn't find some information about the working process inside my libs?

Thanks in advance.

Development Environment: GreenHills

Compiler: ccarm

SDE
  • 129
  • 1
  • 7
  • Assuming this is a unix-like os, the `strip` utility removes extraneous gubbins from executables. –  Feb 12 '17 at 17:40
  • I don't know about your compiler in particular, but every compiler I've used will only generate debug symbols if I specifically requested it via `-g`. – chrisaycock Feb 12 '17 at 17:40
  • @NeilButterworth the strip command (in my case it is called gstrip) can only be used to the final executable/binary not to a static library – SDE Feb 12 '17 at 17:44
  • 1
    Well, in that case, don't compile the libraries with debugging information. –  Feb 12 '17 at 17:48
  • As a *completely* different approach, make him sign an NDA, and ship him the compiled static libraries, and the source. I'm a great believer that source access won't actually help people rip you off much, but will help them debug problems. – Martin Bonner supports Monica Feb 12 '17 at 17:54
  • The approach with an NDA is not a solution for me but thank you @MartinBonner. How can i compile the libs without debug information? – SDE Feb 12 '17 at 18:00
  • @SDE, omit the `-g` compiler flag – Stefan Hegny Feb 14 '17 at 08:50

0 Answers0