X-Originating-Host:	195.154.148.69
Organization:	http://www.remarq.com: The World's Usenet/Discussions Start Here
Subject:	stripping libraries
Lines:	24
From:	Clemens Valens <c DOT valensNOc DOT SPAM AT mindless DOT com DOT invalid>
Newsgroups:	comp.os.msdos.djgpp
Message-ID:	<0755aefe.5d9e585f@usw-ex0101-007.remarq.com>
Bytes:	940
X-Wren-Trace:	ePDV/fzlouijs6ru9Lz09/HD7fz78Lzj5u+x8PbpqeGmo/6gq+Srr6ipuqOn
Date:	Tue, 11 Apr 2000 02:48:00 -0700
NNTP-Posting-Host:	10.0.2.7
X-Complaints-To:	wrenabuse AT remarq DOT com
X-Trace:	WReNphoon4 955446498 10.0.2.7 (Tue, 11 Apr 2000 02:48:18 PDT)
NNTP-Posting-Date:	Tue, 11 Apr 2000 02:48:18 PDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,

I have to create a library to distribute. This library needs to
export only a few functions although internally it uses many.
When I inspect the library file I find all internal function
names etc. that I do not want to be visible. How can I strip all
this?

I have tried "strip --strip-debug -x" but everything is still
there. When I strip using "-K my_symbol" I can get rid of all
the unwanted stuff, but a program that uses this library doesn't
work anymore.

Thanks in advance,
Clemens

P.S. I've built my library from many objects that were compiled
with the -s switch, so there should be no debug info in them.
When I strip debug info from my library the filesize is almost
reduced to a third of the original. So where does all this debug
info come from?

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

- Raw text -