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 t.p.ellison@gmail.com
 designates 64.233.184.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=ghdnloxb5gWUG7TOwmT/zc06frlmXMTkrCfjqH7frhbF1VOyiWFjdkxrZmffS7Q02y4dj9wFs3q+LegUtUvrrtlGq1h9rRXdUF6rjkxVea4Pgf4Uo3q1kj3fQx7SN28Rr4SgNwKdGLFugn53oTYiQGYK+BttxLCpxO2KTwr0I2Y=
Message-ID: <47447727.2000809@gmail.com>
Date: Wed, 21 Nov 2007 18:21:27 +0000
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: [build] Post-build relocation for Harmony
References: <4bebff790711210922g1a31c922kf49879d727fc5aa@mail.gmail.com>
	 <474470E6.7030100@gmail.com>
 <4bebff790711211003k34266749nbabeea8f92e6c6f6@mail.gmail.com>
In-Reply-To: <4bebff790711211003k34266749nbabeea8f92e6c6f6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Aleksey Shipilev wrote:
> That's because editbin can lay out the libraries at once, judging on
> their size. If we will implement the relocation for each of the
> components, we will face the dependencies between them. So I propose
> to relocate the build at once, when all components are built and
> easily accessible.

I see, that makes sense.  So perhaps we should not bother with the
current basing option in makefiles, and just leave it all to the
deployment stage?

Looking at the doc for editbin, I agree that /largeaddressaware looks
like a good option too.  How about /bind ?  Given we just rebased the
DLLs it may help with start-up times?

I may tweak that patch a bit so it doesn't try to rebase the DLLs in the
bin/default directory if the VM isn't DRLVM.  Not sure what the effect
would be on the IBM VME (at least, some of those files don't appear in
the IBM/BEA VM).

Regards,
Tim