From: "S. Lockwood-Childs" <sjl@vctlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-java][PATCH] java-library.bbclass: compatibility with per-recipe sysroots
Date: Wed, 12 Jul 2017 01:36:34 -0700 [thread overview]
Message-ID: <20170712083634.GZ22446@vctlabs.com> (raw)
The removebinaries task was intended to remove pre-built .jar and .class files
from the unpacked source, but when per-recipe sysroots were implemented and
ended up under WORKDIR, .jar or .class in those sysroots inadvertently started
getting killed as well.
For instance, ${WORKDIR}/recipe-sysroot-native/usr/share/java/ecj-bootstrap.jar
was deleted when attempting to build jlex-native... which made javac in
that sysroot rather unhappy.
Solve by excluding both recipe-sysroot and recipe-sysroot-native dirs
from the search-and-destroy operation.
Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com>
---
classes/java-library.bbclass | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/classes/java-library.bbclass b/classes/java-library.bbclass
index 58d5a40..ce1cd28 100644
--- a/classes/java-library.bbclass
+++ b/classes/java-library.bbclass
@@ -50,8 +50,10 @@ ALTJARFILENAMES = "${BPN}.jar"
# Java "source" distributions often contain precompiled things
# we want to delete first.
do_removebinaries() {
- find ${WORKDIR} -name "*.jar" -exec rm {} \;
- find ${WORKDIR} -name "*.class" -exec rm {} \;
+ find ${WORKDIR} ! -path "${RECIPE_SYSROOT}/*" ! -path "${RECIPE_SYSROOT_NATIVE}/*" \
+ -name "*.jar" -exec rm {} \;
+ find ${WORKDIR} ! -path "${RECIPE_SYSROOT}/*" ! -path "${RECIPE_SYSROOT_NATIVE}/*" \
+ -name "*.class" -exec rm {} \;
}
addtask removebinaries after do_unpack before do_patch
--
1.9.4
next reply other threads:[~2017-07-12 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 8:36 S. Lockwood-Childs [this message]
2017-07-21 10:53 ` [meta-java][PATCH] java-library.bbclass: compatibility with per-recipe sysroots Maxin B. John
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=20170712083634.GZ22446@vctlabs.com \
--to=sjl@vctlabs.com \
--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