From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Adding google-breakpad to buildroot
Date: Wed, 23 Apr 2014 23:13:46 +0200 [thread overview]
Message-ID: <53582D0A.2030302@mind.be> (raw)
In-Reply-To: <1398269552.30640.13.camel@mbpro.localhost>
On 23/04/14 18:12, Pascal H?rst wrote:
> On Mit, 2014-04-23 at 17:52 +0200, Samuel Martin wrote:
>> Hi Pascal, Arnout, all,
>>
>> On Wed, Apr 23, 2014 at 5:29 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
>>> On 23/04/14 16:21, Pascal H?rst wrote:
[snip]
>>> It is easier to add it to the target-finalize target. Then you can be
>>> sure that the ordering is correct (target-finalize already has all the
>>> needed dependencies). You can also easily use conditions there (it's not
>>> inside a define).
>>>
>>> However, I think it will be more appropriate to implement breakpad as an
>>> additional strip alternative. You probably don't want to combine strip
>>> with breakpad...
>>
>> I think breakpad is more like a pre-strip hook, that one can enable or
>> not. But in the end, the target image will be stripped most of the
>> time (at least, this is the way I would use such a feature).
>
> I agree, since the extraction of the symbols should always happen, when
> breakpad is used, no mater what strip alternative is selected
OK, I thought breakpad did stripping already.
In that case, I think it's best to put it in target-finalize just before
strip.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 880 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140423/84180dd6/attachment.asc>
next prev parent reply other threads:[~2014-04-23 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 14:21 [Buildroot] Adding google-breakpad to buildroot Pascal Hürst
2014-04-23 15:29 ` Arnout Vandecappelle
2014-04-23 15:52 ` Samuel Martin
2014-04-23 16:12 ` Pascal Hürst
2014-04-23 21:13 ` Arnout Vandecappelle [this message]
2014-04-24 7:52 ` Pascal Hürst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53582D0A.2030302@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.