harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hindess <mark.hind...@googlemail.com>
Subject Re: federated build, classlib build - what am I doing wrong
Date Tue, 29 Apr 2008 10:08:30 GMT

In message <f944d83d0804282235q4ee912e6r8db0824965f17dff@mail.gmail.com>, 
"Alexey Varlamov" writes:
>
> 2008/4/29, Nathan Beyer <nbeyer@gmail.com>:
> > On Mon, Apr 28, 2008 at 6:11 AM, Alexei Fedotov <alexei.fedotov@gmail.com>
> > wrote:
> >
> > > Hello, Nathan,
> > > Your sequence is a pretty robust one. I believe that things are enough
> >
> >
> > Apparently not, since it fails to work. :)
> 
> I recall we chewed this theme few months ago but nothing has changed
> since then.  As long as you do full build of classlib, hythread native
> library is rebuilt (even if you did not touch relevant sources) and
> replaces drlvm's one (in deploy/jdk/jre/bin) thus drlvm fails.

I think the correct solution to this part of the problem would be to use
an API that allows a Harmony VM to provide it's own thread library and
drop the thread library from Harmony Classlib.  Something *exactly* like
the -Dhy.no.thr=true mode:

  https://issues.apache.org/jira/browse/HARMONY-3090

> Alexei does only partial build and it works unless includes hythread.
> But I wonder why classlib natives are rebuilt each time.

I was wondering about this the other day.  The main issue is that
the build-native.xml ignores the build.module option.  Due to the
dependencies it is more difficult to implement but I think something
might be done to improve things a little.

-Mark.



Mime
View raw message