From: Robert Schuster <thebohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Cc: Thomas Haase <t.haase@tarent.de>
Subject: OpenJDK recipes merged
Date: Fri, 09 Jul 2010 12:30:06 +0200 [thread overview]
Message-ID: <4C36FA2E.6020507@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Behold!
Henning merged all the OpenJDK-related recipes which means that from now
on it is not necessary anymore to use the Jalimo overlays for those. I
know that some people were nearly giving up on whether this happens
anytime but if you have a look at the actual files you'll see that an
OpenJDK-build is a complex beast and that is true although there is
already a fine harness called IcedTea around it, that takes a great
share of making the build process simpler.
I personally thank the cool guys at *BugLabs* who are sponsoring the
latest improvements! Everyone else: Go buy more Bugs. :-)
I will soon update the 'Java' page in our wiki and describe how the
build process works. It might also happen that I give a talk at this
year's frOScon (St. Augustin, Germany) about it. AFAIU Ken Gilmer of
BugLabs fame will do the same at this years JavaOne.
Caveats: While the recipes are fine and I think the packaging is of very
high quality, we are experiencing some instability issues with
jamvm-initial which can make it spontaneously crash and therefore let
the OpenJDK build fail. We're on it.
Btw: I was once told by Sun people that building the JDK on an ARM
device takes around 24hrs (!!). A build of the 'openjdk-6' recipe itself
(no dependencies) is around half an hour. Cool?
Enjoy!
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 270 bytes --]
next reply other threads:[~2010-07-09 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 10:30 Robert Schuster [this message]
2010-07-09 10:44 ` OpenJDK recipes merged Koen Kooi
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=4C36FA2E.6020507@gmx.net \
--to=thebohemian@gmx.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=t.haase@tarent.de \
/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