From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5ba2c58c9617ec74,start X-Google-Attributes: gid103376,public From: Stephen Leake Subject: Re: Strip vs. DLL Date: 1998/02/05 Message-ID: <34DA2003.7685@gsfc.nasa.gov>#1/1 X-Deja-AN: 322412379 Content-Transfer-Encoding: 7bit References: <34D6B16E.281C1437@srv.net> Mime-Version: 1.0 Reply-To: Stephen.Leake@gsfc.nasa.gov Content-Type: text/plain; charset=us-ascii Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA Newsgroups: comp.lang.ada Date: 1998-02-05T00:00:00+00:00 List-Id: Paul Whittington wrote: > > Having finally figured out how to build a DLL using GNAT 3.10p1 > I now have a new problem. > > When I run strip on a DLL that works fine it seems to remove the > exported routine names along with all the debug information. No > matter what strip switches I use this happens. > > Is there a way to strip a DLL without also stripping the ability to > use exported routines by name? I don't have a direct answer, but if the purpose of using 'strip' is to remove debugging information, you could always recompile without -g. This is one reason to have a "release build" as well as a "debug build" makefile. > > -- > Paul Whittington > Whittington Engineering > 260 South Woodruff Avenue > Suite 201 > Idaho Falls, ID 83401 > paul@srv.net > > --------------------------------------------------------------- > > Name: smime.p7s > Part 1.2 Type: application/x-pkcs7-signature > Encoding: base64 > Description: S/MIME Cryptographic Signature -- - Stephe