yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Robert Joslyn <robert.joslyn@redrectangle.org>
To: Richard Leitner <richard.leitner@skidata.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
	"dspore@parraid.com" <dspore@parraid.com>
Subject: Re: [yocto] Adding openjdk-11 to Yocto
Date: Tue, 31 Jan 2023 06:39:08 -0800	[thread overview]
Message-ID: <5FFCF910-A57E-4369-9D88-12FCC585E778@redrectangle.org> (raw)
In-Reply-To: <GV0P278MB02110F36ACEAFD3C29936CBCF0D39@GV0P278MB0211.CHEP278.PROD.OUTLOOK.COM>


> On Jan 30, 2023, at 12:27 PM, Richard Leitner <richard.leitner@skidata.com> wrote:
> 
> Hi David,
> unfortunately none I'm aware of.
> 
> But if you have time to add java 11 (or newer) support to meta-java I can give support/guidance.
> 
> regards;rl


Is there any interest in adding recipes that install pre-built Java binaries to meta-java? I needed a newer Java and the easy way was to make a recipe to install the Adoptium binaries: https://github.com/bobolopolis/meta-adoptium/blob/main/recipes-core/temurin/temurin-jdk-17-bin_17.0.6%2B10.bb

This was fine for my purposes, but obviously there’s tradeoffs to using someones pre-built binary. I can send a patch to add these to meta-java if it would be useful to others.

Thanks,
Robert

  reply	other threads:[~2023-01-31 14:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 17:14 Adding openjdk-11 to Yocto dspore
2023-01-30 20:27 ` [yocto] " Richard Leitner - SKIDATA
2023-01-31 14:39   ` Robert Joslyn [this message]
     [not found]     ` <Y9o+Za7X8j20qRIS@g0hl1n.net>
2023-02-02  3:32       ` Robert Joslyn
2023-02-02  7:18         ` Richard Leitner
2023-02-02 14:02           ` [EXTERNAL] " Spore, David
     [not found]           ` <174006CCF862C3D3.3213@lists.yoctoproject.org>
2023-03-27 13:13             ` Spore, David
2023-03-28  3:13               ` Robert Joslyn
2023-04-04  5:41                 ` Richard Leitner

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=5FFCF910-A57E-4369-9D88-12FCC585E778@redrectangle.org \
    --to=robert.joslyn@redrectangle.org \
    --cc=dspore@parraid.com \
    --cc=richard.leitner@skidata.com \
    --cc=yocto@lists.yoctoproject.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;
as well as URLs for NNTP newsgroup(s).