Mailing-List: contact general-help@gump.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Gump code and data" <general@gump.apache.org>
Received-SPF: pass (hermes.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <00CCC589-6F74-11D9-BA88-003065905854@sbcglobal.net>
References: <200501221218.j0MCIaL4029198@Boron.MeepZor.Com>
 <A926DBF8-6DB9-11D9-BA88-003065905854@sbcglobal.net>
 <m3oeff8b58.fsf@bodewig.bost.de>
 <40D150CE-6DFA-11D9-BA88-003065905854@nonintuitive.com>
 <m3zmyzm590.fsf@bodewig.bost.de>
 <EA5EC0E9-6DFD-11D9-BA88-003065905854@sbcglobal.net>
 <m3651lzuxx.fsf@bodewig.bost.de>
 <00CCC589-6F74-11D9-BA88-003065905854@sbcglobal.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <31AED09B-6F75-11D9-BA88-003065905854@nonintuitive.com>
Content-Transfer-Encoding: 7bit
From: Samuel Andrew McIntyre <fuzzylogic@nonintuitive.com>
Subject: Re: derby build
Date: Wed, 26 Jan 2005 00:35:11 -0800
To: Gump code and data <general@gump.apache.org>

resending with the current account. *sigh*

On Jan 25, 2005, at 2:04 AM, Stefan Bodewig wrote:

> Ideally we'd build everything except the JDBC 2.0 stuff using Gump's
> default.  And build the JDBC 2.0 stuff with JDK 1.3's rt.jar on the
> bootclasspath.

The easiest way to achieve this would be to set the property j13lib to 
the location of the JDK 1.3 jar, and build with 
build.sysclasspath=last. I don't know if this is currently possible, 
but I'm guessing no.

> Is there any sensible split of targets in the build file in order to
> achieve that?

So, I made a first pass at this and it come out to seven splits. In the 
main derby build.xml there are now 7 new targets:

gump_split_1: builds everything up to internal api JDBC 2.0 interfaces
gump_split_2: builds internal api JDBC 2.0 interfaces
gump_split_3: builds up to implementations of JDBC 2.0 interfaces
gump_split_4: builds implementations of JDBC 2.0 interfaces
gump_split_5: builds external api up to JDBC 2.0 interfaces
gump_split_6: builds external api classes for JDBC 2.0
gump_split_7: builds everything else.

So, gump_split_2, 4, and 6 should be built with JDK 1.3's rt.jar, the 
rest can be built with JDK 1.4's rt.jar. They should be built in order. 
Also, I just realized that all of these need to be built with the 
property sane=false, which creates a build with all optimizations 
turned on.

I will try in the future to condense these to a smaller number of 
targets, but I don't currently know if this is possible. With these 
targets, though, i think it might be possible to build derby with gump.

Please let me know if there is more I can do.

Thanks,
andrew


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org