Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of ivan.g.popov@gmail.com
 designates 64.233.182.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=tvlKdS9pX0wekNUn2GsSiC/ivWTxgg8mUYUCf+3JPSdmUO5qGd4W7CScSSZVcPmoI+DWBY5E3ghg3w+PFXgcEoSoeFz/K2cB0MXqpKEsH7NhSFzI9T6G6LfSvfmeBhLSBippp4LqRZjEjws6xfTPyh4o7vZvgwb+ipL1pdWci2M=
Message-ID: <b6cb498e0803050610p4a70ee1em42327cfb7111bdf9@mail.gmail.com>
Date: Wed, 5 Mar 2008 20:10:50 +0600
From: "Ivan Popov" <ivan.g.popov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [jdktools][build] Which is more recommendable build approach for
 jdwp?
In-Reply-To: <94d710af0803050145h5fdf8034r28654ab2467ef6c0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <94d710af0803050108j482a567asc655d9faa69a21c4@mail.gmail.com>
	 <94d710af0803050145h5fdf8034r28654ab2467ef6c0@mail.gmail.com>

It's probably caused by recent modification of drlvm build structure.
Running jdktools tests requires JRE binary, which is copied from drlvm
module. As a workaround you can explicitly set this property with
correct drlvm location in the ant command line.

Thanks.
Ivan

On Wed, Mar 5, 2008 at 3:45 PM, Sean Qiu <sean.xx.qiu@gmail.com> wrote:
> Hi, all
>
>  I can not run the test.
>  It seems the test target point to wrong deploy location.
>
>  >ant test
>
>  /hdk/working_jdktools/build.xml:242: The following error occurred
>  while executing this line:
>  /hdk/working_jdktools/make/build-test.xml:104:
>  /hdk/working_vm/build/deploy/jdk/jre not found.
>
>
>  <property name="external.drlvm.loc" value="../working_vm/build/deploy" />
>  Is it should be pointed to  ../working_vm/deploy"?
>
>
>  2008/3/5, Sean Qiu <sean.xx.qiu@gmail.com>:
>
>
> > I have found that we have two approaches to build jdwp.
>  >
>  >  1. Through federated build, this will call the make to build jdwp modules.
>  >   a) cd <jdktools>
>  >   b) ant fetch-depends
>  >   c) ant
>  >
>  >  2. Through jpda module's make directory , this approach will call cc
>  >  directly to build jdwp module.
>  >   a) cd <jdktools>\modules\jpda\make
>  >   b) ant build.jdwp.agent
>  >       ant build.jdwp.transport
>  >
>  >  The first approach works fine, but it seems it does not supply any
>  >  test target.(Am i missing something?)
>  >
>  >  The second approach seems a little outdated,  since the directory
>  >  structure is different from current status and it demands some
>  >  modifications to work. It contains a target to run the junit test.
>  >
>  >  I guess the second is the original script before jdktools are included
>  >  in federated build. So we should just using the first one?
>  >
>  >  Best Regards
>  >
>  >
>  >  --
>  >  Sean, Xiao Xia Qiu
>  >  China Software Development Lab, IBM
>  >
>
>
>  --
>  Sean, Xiao Xia Qiu
>  China Software Development Lab, IBM
>