[Development] Not stripping our binaries by default

[lars.knoll at nokia.com]

On Sep 13, 2012, at 10:21 PM, ext Thiago Macieira <thiago.macieira at intel.com> wrote:

> 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

Depends on who we're optimising for. If we don't strip by default we might get lots of complaints from people compiling source packages on their own that wonder about huge binaries in release mode.

Cheers,
Lars
> 
> 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
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development