[oe-issues] [Bug 2730] New: updated recipes for new classpath versions
bugzilla-daemon at tinman.treke.net
bugzilla-daemon at tinman.treke.net
Fri Aug 10 11:38:39 CEST 2007
http://bugs.openembedded.org/show_bug.cgi?id=2730
Summary: updated recipes for new classpath versions
Product: Openembedded
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Distributions
AssignedTo: openembedded-issues at lists.openembedded.org
ReportedBy: thebohemian at gmx.net
Created an attachment (id=1793)
--> (http://bugs.openembedded.org/attachment.cgi?id=1793)
contents of packages/classpath (untar in empty folder!)
I want to have updated bitbake files of GNU Classpath in OE.
When newer classpaths versions where not buildable due to gtk+ requirements
someone added a 'headless' variant of classpath called classpath-minimal. This
variant is practical for other purposes, too. E.g. in case you want to reach
the GUI through the java-gnome bindings or escher (pure X11 protocol) or just
want to save some flash space.
I see that there is a need for a fast-compiling version of classpath having no
packages itself. However I think it is misleading to such a package
classpath-minimal as well. Therefore I propose classpath-nopackage.
Attached are bitbake files for classpath, classpath-minimal and
classpath-nopackage variants for the latest release 0.95. The files in the
archive resemble how I would like to see the contents of packages/classpath
(excluding files/ ).
It is clear to me that recipes for older classpath versions have to be adjusted
since I edited classpath.inc a lot. I will do so when there a no issues left
with the proposed approach. (However as a GNU Classpath contributor I would say
that older versions of the library are not that useful anymore.)
Btw: I have seen bug 2523 and am aware of what it would take to solve it.
--
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Openembedded-issues
mailing list