Niki Kovacs <mickey@mouse.com> wrote:
> I've been spending some time with studying a bunch of SlackBuild scripts. I
> don't quite understand what that "stripping" is exactly about? What is it?

After compilation of an executable the file contains text strings which
describe the names of the functions and variables. Having such information
in executable and libraries makes it easier to reverse-enginer or debug
them. On the other hand, this information also takes some space.

> What do I need it for? Is there a different stripping process for binaries
> (well, things that go in /usr/bin) and libraries (things that go
> in /usr/lib)?

The command to strip the binaries are simply called "strip". There is a
man-page for that command.

To save some space it is usually a good idea to strip binaries and
libraries at installation. However, there are some exceptions. X is one
such exception where stripped drivers will not work.

How are things going with your transcode SlackBuild script? I have started
working on a Makefile framework for installing software with complex
dependencies. It is being published at http://makepack.sourceforge.net/
however, at the time of this writing it is only a framework. I haven't
populated it with rules for so many applications yet and documentation
remains.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc7(at)uthyres.com Examples of addresses which go to spammers:
root@variousus.net root@localhost