From:	"Campbell, Rolf [SKY:1U32:EXCH]" <moscoop AT americasm01 DOT nt DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: stripping libraries
Date:	Tue, 11 Apr 2000 15:36:13 -0400
Organization:	Nortel Networks
Lines:	23
Message-ID:	<38F37EAD.8DBC7731@americasm01.nt.com>
References:	<0755aefe DOT 5d9e585f AT usw-ex0101-007 DOT remarq DOT com>
NNTP-Posting-Host:	wmerh0tk.ca.nortel.com
Mime-Version:	1.0
X-Mailer:	Mozilla 4.72C-CCK-MCD [en] (X11; I; HP-UX B.10.20 9000/785)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Clemens Valens wrote:

> 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?

Declare any functions that you don't want externally visible as static.

> 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?

The compiler.

--
(\/) Rolf Campbell (\/)

- Raw text -