From: Pascal Huerst <pascal.huerst@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V4 2/2] google-breakpad: integration into makefile and Config.in
Date: Wed, 4 Jun 2014 13:32:53 +0200 [thread overview]
Message-ID: <1401881573-12921-3-git-send-email-pascal.huerst@gmail.com> (raw)
In-Reply-To: <1401881573-12921-1-git-send-email-pascal.huerst@gmail.com>
This adds the symbol generation for google-breakpad to
the Makefile and adds a list were users can insert libraries
and binaries that should be symbol-dumped.
Signed-off-by: Pascal Huerst <pascal.huerst@gmail.com>
---
Config.in | 10 ++++++++++
Makefile | 7 +++++++
package/Config.in | 1 +
3 files changed, 18 insertions(+)
diff --git a/Config.in b/Config.in
index 0799cb7..0849146 100644
--- a/Config.in
+++ b/Config.in
@@ -457,6 +457,16 @@ config BR2_OPTIMIZE_S
endchoice
+config BR2_GOOGLE_BREAKPAD_INCLUDE_FILES
+ string "executables and libraries to be used by google-breakpad"
+ depends on BR2_PACKAGE_GOOGLE_BREAKPAD
+ default ""
+ help
+ You may specify a space-seperated list of binaries and libraries
+ here of which debug symbols should be dumped for google breakpad.
+ Debug symbols will be stored as google_breakpad_symbols in:
+ staging/usr/shared/google-breakpad-symbols
+
config BR2_ENABLE_SSP
bool "build code with Stack Smashing Protection"
depends on BR2_TOOLCHAIN_HAS_SSP
diff --git a/Makefile b/Makefile
index 0b4264a..2650a93 100644
--- a/Makefile
+++ b/Makefile
@@ -553,6 +553,13 @@ endif
ifeq ($(BR2_PACKAGE_PYTHON_PYC_ONLY)$(BR2_PACKAGE_PYTHON3_PYC_ONLY),y)
find $(TARGET_DIR)/usr/lib/ -name '*.py' -print0 | xargs -0 rm -f
endif
+ifeq ($(BR2_PACKAGE_GOOGLE_BREAKPAD),y)
+ package/google-breakpad/google-breakpad-gen-syms.sh \
+ $(STAGING_DIR) \
+ $(HOST_DIR) \
+ "$(call qstrip,$(BR2_GOOGLE_BREAKPAD_INCLUDE_FILES))"
+endif
+
rm -rf $(TARGET_DIR)/usr/lib/luarocks
$(STRIP_FIND_CMD) | xargs $(STRIPCMD) 2>/dev/null || true
if test -d $(TARGET_DIR)/lib/modules; then \
diff --git a/package/Config.in b/package/Config.in
index ea94f01..47cb483 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -786,6 +786,7 @@ source "package/fftw/Config.in"
source "package/flann/Config.in"
source "package/glibmm/Config.in"
source "package/gmp/Config.in"
+source "package/google-breakpad/Config.in"
source "package/gsl/Config.in"
source "package/gtest/Config.in"
source "package/libargtable2/Config.in"
--
1.9.3
next prev parent reply other threads:[~2014-06-04 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 11:32 [Buildroot] [PATCH V4 0/2] google-breakpad: new package Pascal Huerst
2014-06-04 11:32 ` [Buildroot] [PATCH V4 1/2] " Pascal Huerst
2014-06-04 19:53 ` Yann E. MORIN
2014-06-05 20:21 ` Pascal Hürst
2014-06-05 20:28 ` Yann E. MORIN
2014-06-09 17:41 ` Samuel Martin
2014-06-04 11:32 ` Pascal Huerst [this message]
2014-06-04 19:59 ` [Buildroot] [PATCH V4 2/2] google-breakpad: integration into makefile and Config.in Yann E. MORIN
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=1401881573-12921-3-git-send-email-pascal.huerst@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox