All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Robert Schuster <theBohemian@gmx.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: merging recipes from Jalimo
Date: Wed, 12 Dec 2007 23:13:54 +0200	[thread overview]
Message-ID: <208459064.20071212231354@gmail.com> (raw)
In-Reply-To: <476005E5.5050605@gmx.net>

Hello Robert,

Wednesday, December 12, 2007, 6:01:41 PM, you wrote:

> Hi Leon,

> Leon Woestenberg schrieb:
>> Hello Robert,
>> I see the compile task assumes the availability of "javac".
>> 
>> javac -d build -source 1.4 -sourcepath source `cat $list`;
>> 
>> How do you expect this to be available on the host? Will any javac
>> that's out there be good enough to use?
> A Java 1.4 compatible compiler is needed. That can be the proprietary
> javac, gcj -C, jikes and ecj. Most distribution have some way to let the
> latter three be available as 'javac'.

> You may say that we could use jikes-native from OE then but that
> compiler needs (as all Java compilers) a class library. Jikes is not
> Java5-capable but GNU Classpath expects one since version 0.95. One
> could build an older GNU Classpath release just for this purpose but
> then there would still be no runtime to use ecj-bootstrap (which is a
> Java app itself). Additionally I wanted to stick with latest and
> greatest GNU Classpath (especially everything after the Java5 switch)
> releases since the older ones contain surprising bugs and miss important
> tools (gjar, gjavah etc).

> It is really a messy bootstrapping situation, I know. Since OE expects
> GCC being installed I think that gij and gcj can also be available on
> those systems.

>> Currently, OpenEmbedded tries to rely on a defined set of host tools
>> to be installed, and my concern is that we now must add one (out of a
>> set of acceptable) java compiler to that external dependency list. If
>> so, we must do so carefully.
> Yes, thats true. A java compiler and a runtime (both from the fairly old
> 1.4 times) are needed in the beginning. After ecj-bootstrap is built its
> only purpose is to built OE's own java runtime and compiler.

> If independence from those two pieces of software is important I could
> look into this. However I expect this to become complicated.

  As was discussed lately on this list, we should track the expected
host dependencies. This is done using ASSUME_PROVIDED in
conf/bitbake.conf. So, based on the above, I think you want to add
javac-native and java-runtime-native there. Then, your recipe should
DEPENDS on them, and in comment, please include the relevant
additional info above. This should be good compromise, as indeed,
complete self-bootstrapping would be a task in itself, sidetracking you
from the current work.


> Regards
> Robert




-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2007-12-12 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 18:42 RFC: merging recipes from Jalimo Robert Schuster
2007-12-12 13:29 ` Leon Woestenberg
2007-12-12 16:01   ` Robert Schuster
2007-12-12 21:13     ` Paul Sokolovsky [this message]
2007-12-15 13:30       ` Leon Woestenberg
2007-12-19 13:54 ` Robert Schuster

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=208459064.20071212231354@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=theBohemian@gmx.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.