Re: cldc and midp java
On Wed, Sep 12, 2007 at 10:44:41PM +0200, Robert Schuster wrote:
> Hi,
> I recently started investigating to bring proper java toolchain support
> into OpenEmbedded and began to think about the way this handled in
> similar environments. Due to packaging work for maemo I got my hands on
> cacao-cldc a virtual machine that runs a subset of the J2SE java class
> library.
>
> I want to start a little discussion about the future support of the
> different Java profiles in Debian. In the hope for the best outcome in
> Debian as well as for getting even more insight into the topic to
> support my OE work.
>
> By packaging MIDPath for Maemo I got in contact with a third Java
> standard namely J2ME or more specifically MIDP2.0 .
>
> With cacao we have a JVM codebase that can be compiled to run either GNU
> Classpath (~J2SE1.5), soon Icedtea (J2SE1.6; which is to become OpenJDK
> hopefully) and midpath-cldc (CLDC1.1; slightly modified cldc.jar from
> Sun's PhoneME project).
>
> MIDPath in conjunction with either a CLDC or (inclusive!) J2SE providing
> runtime can provide the MIDP2.0 profile.
>
> Last but not least. Sun's PhoneME is free software too and could be
> installed to provide CLDC as well.
>
> Now Debian like every other distribution has no notion of these
> different Java profiles. It only knows javaX-runtime and
> java[2]-compiler and java-virtual-machine. These are virtual packages
> for either development purposes or the smaller runtime-only variants.
> These packages implicitly assume talking about "J2SE".
>
> How is Debian going support the other profiles?
Currently there is no plan is supporting the other profiles. That doesnt
mean we dont want to. I think we can just include phoneme and midpath
and a special cacao build in Debian with normal dependencies. We dont
need to invent virtual package names to depend on or provide yet. We can
do this when we need them.
Cheers,
Michael
Reply to: