From: Jim Fehlig <jfehlig@novell.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] [RFC] Add libxen to overall xen build
Date: Wed, 29 Nov 2006 18:01:28 -0700 [thread overview]
Message-ID: <456E2D68.800@novell.com> (raw)
In-Reply-To: <20061128163408.GK17436@leeni.uk.xensource.com>
Ewan Mellor wrote:
> On Wed, Nov 22, 2006 at 03:03:31PM -0700, Jim Fehlig wrote:
>
>
>> libxen (c-bindings to new XenAPI) is not integrated into the overall xen
>> build. This patch enables building of libxen when 'LIBXENAPI_BINDINGS
>> ?= y' in Config.mk.
>>
>> Headers are installed in $(DESTDIR)/usr/include/xen/api and libs in
>> $(DESTDIR/usr/$(LIBDIR). I did not include the test_bindings program
>> since it introduces yet another dependency - libcurl.
>>
>
> Applied, thanks Jim. Are you going to integrate docs/xen-api into the build
> as well?
>
Ah, forgot about the docs :-/. I'll put it on my todo-list - to be done
after next week's ManDev conference.
Jim
next prev parent reply other threads:[~2006-11-30 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 22:03 [PATCH] [RFC] Add libxen to overall xen build Jim Fehlig
2006-11-28 16:34 ` Ewan Mellor
2006-11-30 1:01 ` Jim Fehlig [this message]
2006-11-30 8:33 ` Ewan Mellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=456E2D68.800@novell.com \
--to=jfehlig@novell.com \
--cc=ewan@xensource.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.