harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Petrenko" <alexey.a.petre...@gmail.com>
Subject Re: [tools][launcher] Where should the launcher code reside?
Date Thu, 03 May 2007 14:16:17 GMT
2007/5/3, Mikhail Loenko <mloenko@gmail.com>:
> I agree. jdktools is something more natural for launcher.
>
> we may require something like working_tools dir next to classlib so
> them classlib build takes it there
There is working_jdktool dir already.

SY, Alexey

>
> Thanks,
> Mikhail
>
> 2007/5/3, Alexey Petrenko <alexey.a.petrenko@gmail.com>:
> > I think that luni module of class library is not the correct place for
> > launcher... jdktools looks much better.
> >
> > SY, Alexey
> >
> > 2007/5/3, Tim Ellison <t.p.ellison@gmail.com>:
> > > Up until yesterday we had two copies of the launcher code, one in
> > > classlib LUNI module, and one in jdktools.  Hopefully we all agree that
> > > we don't need two copies of the code.
> > >
> > > Yesterday I removed the launcher from classlib, and updated the one in
> > > jdktools; but that seems to break a number of people who rely on
> > > building classlib and dropping in a built VM to run a JRE.
> > >
> > > Arguably, the 'right' way to work is either to build an HDK from scratch
> > > (i.e. a full federated build), or download a pre-built HDK then
> > > build&test the classlib|vm|jdktools against that.  Then you will always
> > > have a full installation, and can update the bits you are working on.
> > >
> > > But if people want to keep working with just the classlib and VM then I
> > > have no objection to leaving the launcher in the classlib area.  It
> > > doesn't do anyone any harm in there.  The layout should suit our working
> > > patterns, not the other way around.
> > >
> > > What do you think?
> > >
> > > Tim
> > >
> >
>

Mime
View raw message