harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess" <mark.hind...@googlemail.com>
Subject awt and swing integration issues
Date Sun, 18 Jun 2006 18:04:12 GMT

The outstanding change mentioned in the previous note is an integration
of the java code into new modules:


and replacement the existing awt stubs.

I've only moved java code.  The native code is still built
using the original contributed ant files and even then only if
"-Dwith.awt.swing=true" is set on the ant command line.

I don't intend to integrate the native code right away.  My reasoning

a) It will break everyone build unless they have all the dependencies
(libjpeg, libpng, and liblcms) in the right place.  I want to give
people time to discuss how to handle this.  On linux, these packages
are very common so we really should use the installed dynamic libraries
if possible.  Using liblcms and libjpeg should be easy since they both
use "pkg-config" (as in "pkg-config --cflags lcms" and "pkg-config
--libs lcms") if their development packages are installed.  We'll need
collect details of the required packages for different distributions.
Debian packages are liblcms1-dev, libjpeg-dev (virtual package) and
libpng12-dev.  Anyone fill in the gaps for other distributions?

Not sure what to do on windows. libjpeg and libpng seem to be available
in the MinGW Package repository at:


Anyone tried using these to meet the requirements on Windows?

b) Oliver is about to split the natives and I want to do these natives
the new way.  (So I'll let him do a couple of modules for me to copy!

c) I'm also wondering about the motivation for using C++ when I can't
see any pressing reason to require this.


Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message