Re: [OpenWrt-Devel] Adding host Java support to the buildbots

[Dana Myers]

On 1/2/2017 12:22 AM, Ralph Sennhauser wrote:

On Fri, 30 Dec 2016 06:52:32 -0800
Dana Myers  wrote:


On 12/29/2016 11:50 PM, Ralph Sennhauser wrote:




Another alternative to hotspot on mips would be cacao, again with
openjdk classpath. Though jamvm certainly is a vaild pick.


Without revisiting my selection process from 3 years ago, I did look at the
various alternatives and picked JamVM, and it has proven more than adequate
for my needs. Same thing is true for GNU Classpath.

I needed support for what was historically called the "Connected Device 
Configuration,
Foundation Profile" and the combination of JamVM and Classpath met/meets my 
needs.
Keep in mind that the class of device running OpenWRT is likely to be very 
limited in
terms of memory, and headless as well.

In modern Java terms, I suppose this class of embedded Java use is most
consistent with the "General Connection Framework".


What encumbrance concerns do you have in mind? Debian also ships the
binaries as in openjdk-7-jdk.


Frankly, it was uncertainty on my part regarding embedded use under the
OpenJDK license. It may not be an issue at all; I was more comfortable with
GNU Classpath, it suited my needs, and had the longest history of use with
JamVM (increasing my confidence in stability). I didn't dig into the OpenJDK
licensing details with respect to embedded use.


I don't object to jamvm with gnu classpath, just that I was wondering
why you'd pick it over the alternatives. Basically it's adding java
support that is hardly usable this days apart of a few specialized
cases.


That sounds like a bit of an exaggeration there :-) There's no reason that
support for OpenJDK library and/or additional JVMs can't be integrated into
OpenWRT, though.

Cheers,
Dana
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Adding host Java support to the buildbots

[Ralph Sennhauser]

On Fri, 30 Dec 2016 06:52:32 -0800
Dana Myers  wrote:

> On 12/29/2016 11:50 PM, Ralph Sennhauser wrote:
> > Hi Dana
> >
> > On Thu, 29 Dec 2016 12:30:37 -0800
> > Dana Myers  wrote:
> >  
> >> In reference to https://github.com/openwrt/packages/pull/3686
> >>
> >> We've added OpenWRT support for:
> >>
> >> * JamVM 2.0: Java JVM
> >> * GNU Classpath 2.0: Java class library  
> > There is no classpath 2.0  
> 
> Right you are - serves me right for spewing version numbers off the
> top of my head from something I initially did two years :-) It's
> classpath 0.99
> >  
> >> * RXTX Java serial communications library
> >>
> >> However, the build bots won't build these packages yet because
> >> a host Java compiler is required. To build these packages, I
> >> install:  
> > The main reason to use jamvm with gnu classpath is you can
> > bootstrap it without a jdk, right? If you already require a host
> > jdk why not go for jamvm with the openjdk classpath to get full
> > java support?  
> 
> I don't understand the question about bootstrapping and host vs
> target JDK. Host JDK is used specifically for javac to compile Java
> to bytecodes; target has no dependency on JDK otherwise.

Well, if you require openjdk-7-jdk on the build host you sidestep
bootstrapping java all together (c compiler & source code -> build) in
which case jamvm with openjdk classpath is as easy to get as with gnu
classpath but the latter only supports part of 1.5 & 1.6.

The question boils down to why you settle for something inferior when
you can have something much better.

> 
> Classpath was, for many years, the only library supported by JamVM,
> is much smaller than OpenJDK (valuable on resource-constrained
> systems) and remains the default library supported by JamVM. For the
> purposes of my project from which I contributed, Classpath is
> adequate and appears to avoid concerns about encumbrance of the
> target builds/devices with OpenJDK. Most specifically, however, was
> the apparent lack of support for MIPS32 which is a show-stopper for
> the AR71xx architecture I'm using.

Another alternative to hotspot on mips would be cacao, again with
openjdk classpath. Though jamvm certainly is a vaild pick.

What encumbrance concerns do you have in mind? Debian also ships the
binaries as in openjdk-7-jdk.

I don't object to jamvm with gnu classpath, just that I was wondering
why you'd pick it over the alternatives. Basically it's adding java
support that is hardly usable this days apart of a few specialized
cases.

Cheers
Ralph
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Adding host Java support to the buildbots

[Dana Myers]

On 12/29/2016 11:50 PM, Ralph Sennhauser wrote:

Hi Dana

On Thu, 29 Dec 2016 12:30:37 -0800
Dana Myers  wrote:


In reference to https://github.com/openwrt/packages/pull/3686

We've added OpenWRT support for:

* JamVM 2.0: Java JVM
* GNU Classpath 2.0: Java class library

There is no classpath 2.0


Right you are - serves me right for spewing version numbers off the top
of my head from something I initially did two years :-) It's classpath 0.99



* RXTX Java serial communications library

However, the build bots won't build these packages yet because
a host Java compiler is required. To build these packages, I
install:

The main reason to use jamvm with gnu classpath is you can bootstrap it
without a jdk, right? If you already require a host jdk why not go for
jamvm with the openjdk classpath to get full java support?


I don't understand the question about bootstrapping and host vs target JDK.
Host JDK is used specifically for javac to compile Java to bytecodes; target has
no dependency on JDK otherwise.

Classpath was, for many years, the only library supported by JamVM, is much
smaller than OpenJDK (valuable on resource-constrained systems) and remains
the default library supported by JamVM. For the purposes of my project from 
which
I contributed, Classpath is adequate and appears to avoid concerns about 
encumbrance
of the target builds/devices with OpenJDK. Most specifically, however, was the 
apparent
lack of support for MIPS32 which is a show-stopper for the AR71xx architecture 
I'm using.

If someone is interested in contributing OpenJDK, I'd be happy to consult.




  openjdk-7-jdk

(which also pulls in openjdk-7-jre and openjdk-7-jre-headless)

What needs to be done to add openjdk-7-jdk to the build bots?


Something like 'apt-get install openjdk-7-jdk' (if I recall correctly, still on 
coffee #1
here).

Cheers,
Dana
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Adding host Java support to the buildbots

[Ralph Sennhauser]

Hi Dana

On Thu, 29 Dec 2016 12:30:37 -0800
Dana Myers  wrote:

> In reference to https://github.com/openwrt/packages/pull/3686
> 
> We've added OpenWRT support for:
> 
> * JamVM 2.0: Java JVM
> * GNU Classpath 2.0: Java class library

There is no classpath 2.0

> * RXTX Java serial communications library
> 
> However, the build bots won't build these packages yet because
> a host Java compiler is required. To build these packages, I
> install:

The main reason to use jamvm with gnu classpath is you can bootstrap it
without a jdk, right? If you already require a host jdk why not go for
jamvm with the openjdk classpath to get full java support?

> 
>  openjdk-7-jdk
> 
> (which also pulls in openjdk-7-jre and openjdk-7-jre-headless)
> 
> What needs to be done to add openjdk-7-jdk to the build bots?
> 
> Thank you,
> Dana
> 
> danak6jq@github
> k...@comcast.net
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Adding host Java support to the buildbots

[Dana Myers]

In reference to https://github.com/openwrt/packages/pull/3686

We've added OpenWRT support for:

* JamVM 2.0: Java JVM
* GNU Classpath 2.0: Java class library
* RXTX Java serial communications library

However, the build bots won't build these packages yet because
a host Java compiler is required. To build these packages, I
install:

openjdk-7-jdk

(which also pulls in openjdk-7-jre and openjdk-7-jre-headless)

What needs to be done to add openjdk-7-jdk to the build bots?

Thank you,
Dana

danak6jq@github
k...@comcast.net
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel