On 08-01-16 10:48, Jens Rehsack wrote:
Am 08.01.2016 um 08:39 schrieb Mike Looijmans <mike.looijm...@topic.nl>:
Someone in our project decided he wanted Java on the board, so I just added
"meta-java" to the layers and attempted to follow the README.
So without a clue as to what I'm really doing (I haven't touched Java in 15
years) I added these to my local.conf:
# Headless java
PREFERRED_PROVIDER_classpath = "classpath-minimal"
# Possible provider: cacao-initial-native and jamvm-initial-native
PREFERRED_PROVIDER_virtual/java-initial-native = "cacao-initial-native"
# Possible provider: cacao-native and jamvm-native
PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
And of course added meta-java to bblayers.conf.
I added "openjdk-8" to the image's things to install, and let things build.
While building "openjdk-8-native", things went south, and I get the following
error message:
ERROR: no configure script found at
/home/mike/projects/.../build/tmp-glibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/configure
What did I do wrong?
meta-java is master, so you need poky on master, too - or cherry-pick the
autotools.bbclass patch
I was close to master already, but apparently not close enough.
Upgrading everything to current master results in:
ERROR: ParseError at
/home/mike/projects/.../meta-oe/meta-oe/recipes-extended/sip/sip_4.16.4.bb:19:
Could not inherit file classes/qmake2.bbclass
(Note: the board does not have a display, so I don't need/want x11. I tried
building openjdk-7 instead, but that fails to parse because it requires x11 in
the distro)
You could port the remove-x11-patches to openjdk-7, since we currently need Java8, I have
no "business case" to fix openjdk-7 :/
I don't care either, I'm happy when "helloworld.java" runs on target.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
--
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel