I searched through the GCC mailing lists to find an answer, but I guess I'll get it here quicker:
How much of the recent work on gcj can we expect in gcc4 (and consequently in FC4)? Specifically, will the recent imageio and AWT/cairo improvements from the java-gui-20050128-branch be available?
Thanks,
On Mon, 2005-02-21 at 20:38 +0100, Ziga Mahkovec wrote:
I searched through the GCC mailing lists to find an answer, but I guess I'll get it here quicker:
How much of the recent work on gcj can we expect in gcc4 (and consequently in FC4)? Specifically, will the recent imageio and AWT/cairo improvements from the java-gui-20050128-branch be available?
Yes, all changes on java-gui-20050128-branch have been merged into HEAD. No new work will be done on the gui branch; instead all future GUI work will be done directly on HEAD. If you're on FC3 you can install the Rawhide gcc4 rpms, which track gcc CVS HEAD closely, using yum. Just add the development repository to your yum.conf:
[development] name=Fedora Core $releasever - Development Tree baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearc...
Tom
On Mon, 2005-02-21 at 14:56 -0500, Thomas Fitzsimmons wrote:
Yes, all changes on java-gui-20050128-branch have been merged into HEAD. No new work will be done on the gui branch; instead all future GUI work will be done directly on HEAD.
I forgot to mention: these RPMs will not be built with --enable-gtk-cairo (because cairo will not ship with FC4) so Graphics2D won't be supported by the FC4 gcc4 rpms.
Tom
On Mon, 2005-02-21 at 15:03 -0500, Thomas Fitzsimmons wrote:
I forgot to mention: these RPMs will not be built with --enable-gtk-cairo (because cairo will not ship with FC4) so Graphics2D won't be supported by the FC4 gcc4 rpms.
Too bad, java2d was what I was aiming at. Though now that GTK+ depends on cairo, I guess it won't take long to include it in rawhide at least?
Back to jhbuild then. Given that new work is now done on trunk, I should probably change my .jhbuildrc configuration:
# We need the latest snapshot branch branches['cairo'] = 'SNAPSHOT_0_3_0' # And the latest gui branch for gcj -branches['gcj'] = 'java-gui-20050128-branch' +branches['gcj'] = 'HEAD'
Are there any other changes necessary?
On Mon, 2005-02-21 at 21:28 +0100, Ziga Mahkovec wrote:
On Mon, 2005-02-21 at 15:03 -0500, Thomas Fitzsimmons wrote:
I forgot to mention: these RPMs will not be built with --enable-gtk-cairo (because cairo will not ship with FC4) so Graphics2D won't be supported by the FC4 gcc4 rpms.
Too bad, java2d was what I was aiming at. Though now that GTK+ depends on cairo, I guess it won't take long to include it in rawhide at least?
Back to jhbuild then. Given that new work is now done on trunk, I should probably change my .jhbuildrc configuration:
# We need the latest snapshot branch branches['cairo'] = 'SNAPSHOT_0_3_0' # And the latest gui branch for gcj -branches['gcj'] = 'java-gui-20050128-branch'
Actually, I think you can just remove this line and jhbuild will default to checking out HEAD.
+branches['gcj'] = 'HEAD'
Are there any other changes necessary?
No, I don't think so, though it's been a while since I've used JHBuild to update my tree.
Tom
Hi,
On Mon, 2005-02-21 at 20:38 +0100, Ziga Mahkovec wrote:
How much of the recent work on gcj can we expect in gcc4 (and consequently in FC4)? Specifically, will the recent imageio and AWT/cairo improvements from the java-gui-20050128-branch be available?
The wholeimageio, cairo and gui-branch was merged into trunk (which will become 4.0) last week. So, the short answer is "all of it". It isn't clear whether FC4 will include cairo though. So you might have to do without -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D. It is off by default, and needs to be explicitly enabled by configuring gcc with --enable-gtk-cairo, which is currently not done for the FC4 pre-releases of gcc that I have seen. (Most things work fine without it, just Graphics2D support isn't there then.)
Cheers,
Mark
java-devel@lists.fedoraproject.org
-
Mark Wielaard -
Thomas Fitzsimmons -
Ziga Mahkovec