xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Thanos Makatos <thanos.makatos@citrix.com>
To: xen-devel@lists.xensource.com
Cc: thanos.makatos@citrix.com
Subject: [PATCH 7 of 7 v2] blktap3/tapback: Introduce tapback daemon Makefile
Date: Fri, 4 Jan 2013 12:14:07 +0000	[thread overview]
Message-ID: <84f9d3e16cf19625b560.1357301647@makatos-desktop> (raw)
In-Reply-To: <patchbomb.1357301640@makatos-desktop>

This patch introduces the Makefile that builds the tapback daemon. This
Makefile is not yet hooked into the build system.

diff -r 407ebde55295 -r 84f9d3e16cf1 tools/blktap3/tapback/Makefile
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tools/blktap3/tapback/Makefile	Fri Jan 04 12:10:40 2013 +0000
@@ -0,0 +1,48 @@
+XEN_ROOT := $(CURDIR)/../../../
+include $(XEN_ROOT)/tools/Rules.mk
+
+BLKTAP_ROOT := ..
+
+INST_DIR ?= /usr/bin
+
+IBIN = tapback
+
+# -D_GNU_SOURCE is required by vasprintf.
+override CFLAGS += \
+	-I$(BLKTAP_ROOT)/include \
+	-I$(BLKTAP_ROOT)/control \
+	-D_GNU_SOURCE \
+    $(CFLAGS_libxenstore) \
+    $(CFLAGS_libxenctrl) \
+	$(CFLAGS_xeninclude) \
+    -Wall \
+    -Wextra \
+    -Werror
+
+# FIXME cause trouble
+override CFLAGS += \
+    -Wno-old-style-declaration \
+    -Wno-sign-compare \
+    -Wno-type-limits
+
+override LDFLAGS += \
+    $(LDLIBS_libxenstore) \
+    $(LDFLAGS_libxenctrl)
+
+TAPBACK-OBJS := log.o xenstore.o frontend.o backend.o
+
+TAPBACK-LIBS := $(BLKTAP_ROOT)/control/libblktapctl.so.1.0.0
+
+all: $(IBIN)
+
+$(IBIN): $(TAPBACK-OBJS) tapback.o
+	$(CC) -o $@ $^ $(TAPBACK-LIBS) $(LDFLAGS)
+
+install: all
+	$(INSTALL_DIR) -p $(DESTDIR)$(INST_DIR)
+	$(INSTALL_PROG) $(IBIN) $(DESTDIR)$(INST_DIR)
+
+clean:
+	rm -f *.o *.o.d .*.o.d $(IBIN)
+
+.PHONY: clean install

  parent reply	other threads:[~2013-01-04 12:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 12:14 [PATCH 0 of 7 v2] blktap3: Introduce the tapback daemon (most of blkback in user-space) Thanos Makatos
2013-01-04 12:14 ` [PATCH 1 of 7 v2] blktap3/tapback: Introduce core defines and structure definitions Thanos Makatos
2013-01-18 15:28   ` Ian Campbell
2013-01-25 13:25     ` Thanos Makatos
2013-01-04 12:14 ` [PATCH 2 of 7 v2] blktap3/tapback: Introduces functionality required to access XenStore Thanos Makatos
2013-01-18 16:08   ` Ian Campbell
2013-01-25 14:03     ` Thanos Makatos
2013-01-25 14:13       ` Ian Campbell
2013-01-04 12:14 ` [PATCH 3 of 7 v2] blktap3/tapback: Logging for the tapback daemon and libxenio Thanos Makatos
2013-01-04 12:14 ` [PATCH 4 of 7 v2] blktap3/tapback: Introduce back-end XenStore path handler Thanos Makatos
2013-01-18 17:07   ` Ian Campbell
2013-01-25 14:31     ` Thanos Makatos
2013-01-25 14:38       ` Ian Campbell
2013-01-04 12:14 ` [PATCH 5 of 7 v2] blktap3/tapback: Introduce front-end " Thanos Makatos
2013-01-18 17:17   ` Ian Campbell
2013-01-25 15:09     ` Thanos Makatos
2013-01-25 16:15       ` Ian Campbell
2013-01-04 12:14 ` [PATCH 6 of 7 v2] blktap3/tapback: Introduce the tapback daemon Thanos Makatos
2013-01-04 12:14 ` Thanos Makatos [this message]
2013-01-18 17:21   ` [PATCH 7 of 7 v2] blktap3/tapback: Introduce tapback daemon Makefile Ian Campbell

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=84f9d3e16cf19625b560.1357301647@makatos-desktop \
    --to=thanos.makatos@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).