Re: Another dumb idea: debugging info in .deb's

[Christian Schwarz <schwarz@monet.m.isar.de>]

On Mon, 15 Sep 1997, Jim Pick wrote:

[snip]
> But perhaps we could move a step in this direction right away.  If we
> changed the building process in debian/rules to work this way:
> 
>   1) built all binaries with debugging info
>   2) install binaries into debian/tmp/....
>   3) strip all the binaries under debian/tmp
>   4) rest of debian/rules steps, finishing with building the package file
> 
> Now, if somebody wants a package with debugging info, they can just 
> comment out step 3 in the debian/rules file - and rebuild.  

Not only that this is an excellent idea--this is _current policy_ :-)

<quote>
3.3.1 Binaries 

[...]
Generally the following compilation parameters should be used: 

   CC = gcc 
   CFLAGS = -O2 -g -Wall # sane warning options vary between programs 
   LDFLAGS = # none 
   install -s # (or use strip on the files in debian/tmp)

Note that all installed binaries should be stripped, either by using the
-s flag to install, or by calling strip on the binaries after they have
been copied into debian/tmp but before the tree is made into a package. 

The -g flag is useful on compilation so that you have available a full set
of debugging symbols in your built source tree, in case anyone should file
a bug report involving (for example) a core dump. 
</quote>


Thanks,

Chris

--          _,,     Christian Schwarz
           / o \__   schwarz@monet.m.isar.de, schwarz@schwarz-online.com,
           !   ___;   schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
           \  /        
  \\\______/  !        PGP-fp: 8F 61 EB 6D CF 23 CA D7  34 05 14 5C C8 DC 22 BA
   \          /         http://fatman.mathematik.tu-muenchen.de/~schwarz/
-.-.,---,-,-..---,-,-.,----.-.-
  "DIE ENTE BLEIBT DRAUSSEN!"


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .