From: Anatol Belski <anbelski@microsoft.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH] gperftools: separate off libtcmalloc-minimal
Date: Mon, 22 Jul 2019 00:53:30 +0000 [thread overview]
Message-ID: <20190722005330.69615-1-anbelski@microsoft.com> (raw)
From: Anatol Belski <anatol.oe@belski.net>
From: Anatol Belski <anbelski@microsoft.com>
The libctmalloc-minimal is what is useful for C++ apps if only the
improved allocator is needed. The gperftools package stays otherwise
fully backward compatible as it's going to depend on libtcmalloc-minimal.
The libtcmalloc-minimal can be installed separately, which allows for
more flexibility and for cleaner image contents.
The discussion on the patch
https://patchwork.openembedded.org/patch/163234/ has shown, that a
separate package for other libs might have less sense in this case, so
it's not done. The patch 163234 can be abandoned in favor of this for
now.
Signed-off-by: Anatol Belski <anbelski@microsoft.com>
---
meta-oe/recipes-support/gperftools/gperftools_2.7.bb | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/meta-oe/recipes-support/gperftools/gperftools_2.7.bb b/meta-oe/recipes-support/gperftools/gperftools_2.7.bb
index c8b91278d..c48a98183 100644
--- a/meta-oe/recipes-support/gperftools/gperftools_2.7.bb
+++ b/meta-oe/recipes-support/gperftools/gperftools_2.7.bb
@@ -28,3 +28,11 @@ COMPATIBLE_HOST_mipsarch_libc-glibc = "null"
ARM_INSTRUCTION_SET_armv5 = "arm"
ARM_INSTRUCTION_SET_toolchain-clang_arm = "arm"
+# Ensure static libs are always enabled, as they seem to be not produced by
+# default at least on ARM.
+EXTRA_OECONF_append += " --enable-static"
+
+PACKAGE_BEFORE_PN += "libtcmalloc-minimal"
+FILES_libtcmalloc-minimal = "${libdir}/libtcmalloc_minimal*${SOLIBS} ${libdir}/libtcmalloc_minimal_debug*${SOLIBS}"
+RDEPENDS_${PN} += "libtcmalloc-minimal (= ${EXTENDPKGV})"
+
--
2.17.1
reply other threads:[~2019-07-22 0:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190722005330.69615-1-anbelski@microsoft.com \
--to=anbelski@microsoft.com \
--cc=anatol.oe@belski.net \
--cc=openembedded-devel@lists.openembedded.org \
/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