[Dev] Striping binaries

Stéphane Desneux stephane.desneux at open.eurogiciel.org
Mon Oct 13 10:32:33 GMT 2014


Hi Lukasz,

At least, to have a chance to get debug packages, you shouldn't override
the compiler flags: removing the debug flags for example, is a bad idea.

Finally, IIRC, there was already a discussion on this list about
stripping one year ago. The conclusion was that the binaries still
contain the symbols names to get more readable stack traces/cores
without having to install the debug packages (the binaries are only
partially stripped, on purpose). This may change in the future to reduce
footprint.

Best regards,
-- 
Stéphane Desneux
Intel OTC - Vannes/FR
gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726

On 13/10/2014 12:07, Bartosh, Eduard wrote:
> Stripping binaries is done by default during package build and you don't need to do anything special in this regard.
> 
> -----Original Message-----
> From: Dev [mailto:dev-bounces at lists.tizen.org] On Behalf Of Lukasz Wojciechowski
> Sent: Monday, October 13, 2014 12:56 PM
> To: Stéphane Desneux; dev at lists.tizen.org
> Subject: [Dev] Striping binaries
> 
> Hi
> 
> I searched Tizen wiki pages, but don't find any information about binaries stripping policy in Tizen.
> So I asked here:
> 
> Should binaries (executables and shared libraries) be stripped by makefiles during build time ?
> or should they be left with symbols and will be stripped during image creation or installation time ?
> 
> Best regards
> Lukasz
> _______________________________________________
> Dev mailing list
> Dev at lists.tizen.org
> https://lists.tizen.org/listinfo/dev
> ---------------------------------------------------------------------
> Intel Finland Oy
> Registered Address: PL 281, 00181 Helsinki 
> Business Identity Code: 0357606 - 4 
> Domiciled in Helsinki 
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 


More information about the Dev mailing list