Re: [Xen-devel] [PATCH 4/9] raisin: add a component to build qemu_traditional

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Wed, 15 Apr 2015, Ian Campbell wrote:
> On Wed, 2015-04-15 at 17:15 +0100, Ian Jackson wrote:
> > Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 4/9] raisin: add a 
> > component to build qemu_traditional"):
> > > On Wed, 15 Apr 2015, Ian Campbell wrote:
> > > > (I also think osstest support is a prerequisite for saying it is an
> > > > officially support XenProject thing, but that's offtopic in this
> > > > context)
> > > 
> > > I spoke with IanJ and he didn't seem too keen on adding raisin support
> > > to osstest before raisin could build everything out of tree. That's way
> > > I started tackling qemu and qemu-traditional.
> 
> I see, I had imagined we would prefer a more piecemeal process.
> 
> > I don't mind a hybrid approach.  What I would like is for each
> > subproject to _either_ do the existing thing, or be able to ask raisin
> > about it in advance.
> 
> Isn't that going to be useful/necessary anyway? e.g. as new (i.e.
> completely new, not moving from xen.git) stuff is added and desirable to
> support.

The integration process that I envisioned is something like the
following:

- Add any missing options to the xen-unstable build system to avoid
cloning and building sub-components, such as qemu, seabios, etc. Many of
these configure options are already there, like --with-system-qemu and
--with-system-ovmf.

- build all these components separately in raisin

- introduce raisin in osstest

- disable by default cloning and building sub-components from xen-unstable

/ time passes /

- remove options to clone and build sub-components from xen-unstable

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel