Date: Mon, 25 Feb 2002 09:54:01 -0700 From: Nate Williams <nate@yogotech.com> To: Jay Sachs <jay@eziba.com> Cc: freebsd-java@FreeBSD.ORG Subject: Re: bsd.java.mk and native jdk1.3.1p6 Message-ID: <15482.27689.514402.133071@caddis.yogotech.com> In-Reply-To: <3C7A6A5C.7060908@eziba.com> References: <20020225172933.L50703-100000@puget.esil.univ-mrs.fr> <15482.26816.891227.469480@caddis.yogotech.com> <3C7A6A5C.7060908@eziba.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >>Does the bsd.java.mk effort means we will soon be able to build jdk1.3.1p6 > >>using jikes (with $JAVAC variable correctly set up) ? > >> > > > > Almost certainly not, since the building of the JDK is really tied to > > having an existing JDK for things other than compiling. :( > > > > But does that preclude using jikes for compilation? It might be tricky > to integrate, but it would certainly speed up the build. Sure, but hopefully (knock on wood) we will get a binary release of the JDK out soon enough, such that regular users won't have to compile the JDK at all. The reasons for not using Jikes is not a good idea (IMHO) is: 1) It requires alot of changes to the existing Makefile structure as released from Sun. 2) Even if #1 is done, we would have to maintain these changes on our own, and Sun has shown a propensity to radically change the build environment between releases, such that the work would have to be redone everytime a new release of the JDK was released. 3) The number of times a user has to build the JDK should be *very* small (once every 6 months or so), so the amount of work saved vs. the amount of time saved is very little (IMO). A binary release would solve most of the user problems, so hopefully that will happen soon. (And no, I don't know when it will happen.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15482.27689.514402.133071>