From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: xenstored.h Date: Mon, 12 Sep 2005 21:11:15 +0100 Message-ID: <3d8eece205091213113ec4999@mail.gmail.com> References: <516F50407E01324991DD6D07B0531AD56959E4@cacexc12.americas.cpqcorp.net> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Rik van Riel Cc: "Magenheimer, Dan (HP Labs Fort Collins)" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 9/12/05, Rik van Riel wrote: > On Mon, 12 Sep 2005, Magenheimer, Dan (HP Labs Fort Collins) wrote: >=20 > > 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? >=20 > 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