When/how to build separate debug symbol files

[Marcus Meissner]

On Wed, Jun 24, 2015 at 06:26:31PM -0500, Ken Thomases wrote:
> Hi,
> 
> I'm investigating how to best make Wine build and install debug symbol files on OS X.
> 
> My understanding is that, on Linux, the distros usually provide a
> separate package for a user to install Wine's debug symbols.  From recent
> work in dbghelp, I'm guessing such a package installs debug symbol files
> next to the corresponding binary or in a .debug subdirectory next to it.
> Is that correct?

For SUSE we install the debuginfo in places like:

	/usr/lib/debug/usr/lib64/libusb-1.0.so.0.1.0.debug
for e.g. the libusb 1.0 shared library.
	/usr/lib64/libusb-1.0.so.0.1.0

Other distros might do it differently.
 
> How do packagers generate such separate debug symbol files?  Is it
> a special option (make target?) in Wine's build process?  Or is it a
> post-processing step after Wine is built and installed to a staging
> directory?  How does this interact with stripping during building for
> the non-debug-symbol, normal Wine package?

It is standard macro hidden in our RPM build process. It happens after the
regular package "make install" is done. 

It extracts the debuginfo fully automatic, no packager attention required.

Basically it does objcopy of the debug sections for all libraries and binaries,
and afterwards it does "strip --strip-unneeded"

The package build itself is not supposed to strip binaries.

CIao, Marcus