From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] icu: reduce what's needed for cross tools
Date: Tue, 18 Dec 2012 17:14:28 -0800 [thread overview]
Message-ID: <1355879668-22733-2-git-send-email-sgw@linux.intel.com> (raw)
In-Reply-To: <1355879668-22733-1-git-send-email-sgw@linux.intel.com>
The ICU Update copied to complete source tree over, it only
needed a couple of binaries and libraries, so only copy those.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/recipes-support/icu/icu.inc | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-support/icu/icu.inc b/meta/recipes-support/icu/icu.inc
index f7257d1..1329635 100644
--- a/meta/recipes-support/icu/icu.inc
+++ b/meta/recipes-support/icu/icu.inc
@@ -7,7 +7,7 @@ DEPENDS = "icu-native"
DEPENDS_class-native = ""
S = "${WORKDIR}/icu/source"
-STAGING_ICU_SOURCE_DIR_NATIVE = "${STAGING_DATADIR_NATIVE}/icu"
+STAGING_ICU_DIR_NATIVE = "${STAGING_DATADIR_NATIVE}/${BPN}/${PV}"
PARALLEL_MAKE = ""
FULL_OPTIMIZATION_arm = "-Os"
@@ -17,7 +17,7 @@ inherit autotools pkgconfig binconfig
# ICU needs the native build directory as an argument to its --with-cross-build option when
# cross-compiling. Taken the situation that different builds may share a common sstate-cache
# into consideration, the native build directory needs to be staged.
-EXTRA_OECONF = "--with-cross-build=${STAGING_DATADIR_NATIVE}/icu/source"
+EXTRA_OECONF = "--with-cross-build=${STAGING_ICU_DIR_NATIVE}"
EXTRA_OECONF_class-native = ""
# ICU puts custom m4 autoconf functions in aclocal.m4.
@@ -29,11 +29,13 @@ do_configure_prepend() {
[ -f acinclude.m4 ] || cp aclocal.m4 acinclude.m4
}
-do_install_append() {
- if [ ${PN} == 'icu-native' ]; then
- mkdir -p ${D}/${STAGING_ICU_SOURCE_DIR_NATIVE}
- cp -r ${S} ${D}/${STAGING_ICU_SOURCE_DIR_NATIVE}
- fi
+do_install_append_class-native() {
+ mkdir -p ${D}/${STAGING_ICU_DIR_NATIVE}/config
+ cp -r ${S}/config/icucross.mk ${D}/${STAGING_ICU_DIR_NATIVE}/config
+ cp -r ${S}/lib ${D}/${STAGING_ICU_DIR_NATIVE}
+ cp -r ${S}/bin ${D}/${STAGING_ICU_DIR_NATIVE}
+ cp -r ${S}/tools ${D}/${STAGING_ICU_DIR_NATIVE}
+
}
PACKAGES =+ "libicudata libicuuc libicui18n libicule libiculx libicutu libicuio"
--
1.7.9.5
next prev parent reply other threads:[~2012-12-19 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 1:14 [PATCH 1/2] lsbinitscripts: Don't compile Saul Wold
2012-12-19 1:14 ` Saul Wold [this message]
2012-12-19 5:15 ` Saul Wold
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=1355879668-22733-2-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@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