All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pascal Hürst" <pascal.huerst@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding google-breakpad to buildroot
Date: Wed, 23 Apr 2014 16:21:46 +0200	[thread overview]
Message-ID: <1398262906.30640.4.camel@mbpro.localhost> (raw)

Hi everyone,

we are planing to add google-breakpad to buildroot. 

From the project description at
http://code.google.com/p/google-breakpad/:  

[...] "Breakpad is a library and tool suite that allows you to
distribute an application to users with compiler-provided debugging
information removed, record crashes in compact "minidump" files, send
them back to your server, and produce C and C++ stack traces from these
minidumps." [...]

Adding a package to buildroot is easy, but in this case we will have to
find a way to extract all symbols from the target binaries, before they
get stripped. My idea was to add a new target to the Makefile, just
before "target-finalize:" and check against an option in the config
like:

ifeq ($(BR2_ENABLE_BREAKPAD),y)
        TARGETS+=target-generate-breakpad-symbols
endif

and then:

target-generate-breakpad-symbols:
        extract symbols and deploy result to output/images 

Is this basically the way to go, or is there a better way to achieve
this?

regards,
pascal
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140423/eebac11d/attachment.asc>

             reply	other threads:[~2014-04-23 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 14:21 Pascal Hürst [this message]
2014-04-23 15:29 ` [Buildroot] Adding google-breakpad to buildroot Arnout Vandecappelle
2014-04-23 15:52   ` Samuel Martin
2014-04-23 16:12     ` Pascal Hürst
2014-04-23 21:13       ` Arnout Vandecappelle
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=1398262906.30640.4.camel@mbpro.localhost \
    --to=pascal.huerst@gmail.com \
    --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.