[Releasing] Not stripping our binaries by default
Thiago Macieira
thiago.macieira at intel.com
Thu Sep 13 22:21:21 CEST 2012
I was trying to make Qt 5 packages for Tizen when I realised that the
automated build scripts that generate debuginfo packages were failing, saying
that our libraries are already stripped.
Turns out that qmake generates "strip --strip-unneeded" commands when in
release mode. There's a way to turn it off by passing an extra CONFIG to qmake,
but that is not accessible from the configure command-line.
Either way, stripping by default sounds wrong to me. Distributions already
have their own tools to strip. So I'm proposing that we stop doing that. See
https://codereview.qt-project.org/34835
For our own SDK, we might need to add the stripping at the appropriate
place(s).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20120913/3a6ddbe4/attachment.sig>
More information about the Releasing
mailing list