Xen project Mailing List

Re: [Xen-devel] xenstored.h

From: Christian Limpach <christian.limpach@xxxxxxxxx>

Date: Mon, 12 Sep 2005 21:11:15 +0100

Cc: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx

Delivery-date: Mon, 12 Sep 2005 20:09:27 +0000

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LRwPYPIkpolzZKOY/DWYjuNCt1ekmKIZjhwqBC5dHWVa0tUQKpGD8uUDq8/oVm0audB7Jhnev2625NhL07HSTKa4azIaXYDdumRPwVW3Q4OppwmFkuea3NhH3bWt62W5MnuzRnZCt56vdaemcehEWtwQu2Qq4HuxaALtnHS64vc=

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 9/12/05, Rik van Riel <riel@xxxxxxxxxx> wrote: > On Mon, 12 Sep 2005, Magenheimer, Dan (HP Labs Fort Collins) wrote: > > > Now that xenstore is in the mainline and xenstored.h is > > part of the API to xenlinux, should xenstored.h be > > moved into xen/include/public instead of being > > mkbuildtree'd from tools/xenstore to drivers/xen/xenbus? > > Won't that make it impossible to build xenolinux kernels > outside of the Xen tree - say, kernel RPMs ? Yeah, you need to include those in your source RPMs - or have some kind of xen-headers RPM which you'd then require to build kernels... As Dan pointed out, the same applies for the other files in xen/include/public... christian _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

References:

[Xen-devel] xenstored.h
- From: Magenheimer, Dan (HP Labs Fort Collins)
Re: [Xen-devel] xenstored.h
- From: Rik van Riel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.