> > Note that for dynamic libs, this overhead must remain for > your os to be > able to use the dso or dll, so you cannot strip libfltk.so.
Strictly speaking (to avoid any confusion) you can't strip libfltk.a either on most platforms (not if you want to use it again!) But as Gonzalo said, you can strip your exe if it is statically linked to libfltk.a, and that will save a fair bit of space. In general, stripping your exe is a Good Thing to do in general - unless you plan to run your code from the debugger (since the debugger uses a lot the same symbolic information that the linker uses to resolve symbol names etc.) (Side note: if you build the fltk lib with full debug information enabled, then it gets *a lot* bigger - several MB or so!) To strip your exe at build time, with gcc, add the option "-s" to the last stage of the build (the one that finally links the exe) and that will strip it for you. Alternately, use strip at the command line, as: strip <my_app_name> There are many complex things you can do to strip certain parts of the symbolic information and not others, but those simple options are enough for most uses. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
