Re: Java handling in OpenEmbedded

[Koen Kooi <k.kooi@student.utwente.nl>]

On 07-12-09 19:59, Marcin Juszkiewicz wrote:
>
> Hi
>
> For most of time I do builds of BugLabs software for just one device: BUG
> which uses i.mx31 cpu (armv6). As I need to test it also on BeagleBoard I got
> hit by one problem when it comes to building Java software...
>
> As Java is target independent we package it as "all". But the problem is when
> build want to get JAR files built from other recipes (think dependencies). By
> default all those jars are staged into target staging (armv6-angstrom-linux-
> gnueabi in this case). It works fine as long as you do not want to build for
> other architecture in same tmpdir.
>
> After MACHINE change OE thinks (correctly) that it does not need to build Java
> things again (as it was PACKAGE_ARCH="all") and tries to use it from staging.
> But staging/usr/share/java/ dir is empty...
>
> OK, someone can say "but what is a deal? it got built before so you can just
> install packages - they are 'all' anyway". Sure, but some of our Java recipes
> are bind to BUG kernel services so can not be built for other devices and we
> do not want to be forced to keep MACHINE values in specific order to 'maybe
> this will work' way of building.
>
> What is a solution? I had few ideas during weekend and tested two of them.
>
> 1. Drop PACKAGE_ARCH="all" for ALL Java recipes. It works but adds extra
>     building time.
>
> 2. Change staging of JAR files. This worked fine for my build. Patch to
>     stable/2009 branch attached.

Your proposal sounds good to me. I'm willing to sacrifice some buildtime 
and storage om my buildhosts to retain my sanity when building java stuff :)

regards,

Koen