From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] classpath: bump to version 0.99
Date: Mon, 13 Feb 2017 14:29:52 +0100 [thread overview]
Message-ID: <20170213142952.302e6ee4@free-electrons.com> (raw)
In-Reply-To: <5160b52a-c48a-4b52-3d0e-9d73a6fb5c37@cartelsol.com>
Hello,
On Sun, 12 Feb 2017 16:36:02 +0100, Marcus Hoffmann wrote:
> > 1. If you're using/interested in classpath, would you mind adding your
> > name in the DEVELOPERS file for this package? Same if you're
> > using/interested in jamvm. Those two packages are currently not
> > associated to any developer, it would be nice to have a developer
> > interested in those two packages.
> I don't know, we are looking into jamvm/classpath but haven't decided on
> a Java VM/class library yet. For now I would wait a while until there is
> a decision if we'll be using those packages.
OK.
> > 2. classpath has a "depends on BR2_PACKAGE_JAMVM" and jamvm has a
> > "select BR2_PACKAGE_CLASSPATH" which feels a bit like a circular
> > dependency. It would be nice to fix that up as well.
>
> What would be the preferred solution here? JamVM selecting classpath
> seems fine, as long as there is no alternative class library in
> buildroot. So we allow selecting classpath but not JamVM? Here is a list
> of projects using gnu classpath:
> https://www.gnu.org/software/classpath/stories.html#jvm
My understanding is that the build dependency is:
jamvm -> classpath
i.e the classpath package needs to be built/installed before we build
the jamvm package. If that's the case, then I would keep the "select
BR2_PACKAGE_CLASSPATH" in jamvm/Config.in, but get rid of the "depends
on BR2_PACKAGE_JAMVM" in classpath/Config.in.
Peter, you're the one who added classpath originally (commit
5062f530081913bd0487f0f879be180f30836ab8) including this "depends on
BR2_PACKAGE_JAMVM" dependency. What do you think ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-13 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 1:47 [Buildroot] [PATCH 1/1] classpath: bump to version 0.99 Marcus Hoffmann
2017-02-12 1:54 ` [Buildroot] [PATCH v2] " Marcus Hoffmann
2017-02-12 2:04 ` [Buildroot] [PATCH v3] " Marcus Hoffmann
2017-02-12 14:14 ` Thomas Petazzoni
2017-02-12 15:36 ` Marcus Hoffmann
2017-02-13 13:29 ` Thomas Petazzoni [this message]
2017-02-13 15:08 ` Marcus Hoffmann
2017-02-13 16:05 ` Peter Korsgaard
2017-02-13 16:09 ` Thomas Petazzoni
2017-02-13 16:27 ` Peter Korsgaard
2017-02-13 16:46 ` Thomas Petazzoni
2017-02-12 14:41 ` Thomas Petazzoni
2017-02-12 15:00 ` Marcus Hoffmann
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=20170213142952.302e6ee4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.