qubes-core-admin-linux/qrexec/Makefile

CC=gcc
CFLAGS+=-I. -g -Wall -Wextra -Werror -pie -fPIC `pkg-config --cflags vchan-$(BACKEND_VMM)`
LIBS=`pkg-config --libs vchan-$(BACKEND_VMM)` -lqrexec-utils


all: qrexec-daemon qrexec-client 
qrexec-daemon: qrexec-daemon.o
	$(CC) -pie -g -o qrexec-daemon qrexec-daemon.o $(LIBS)
qrexec-client: qrexec-client.o
	$(CC) -pie -g -o qrexec-client qrexec-client.o $(LIBS)
clean:
	rm -f *.o *~ qrexec-daemon qrexec-client
Add qrexec back, use qubes-utils libraries for common code 2013-03-20 05:24:17 +00:00			`CC=gcc`
update for new vchan API 2013-04-22 03:16:10 +00:00			CFLAGS+=-I. -g -Wall -Wextra -Werror -pie -fPIC `pkg-config --cflags vchan-$(BACKEND_VMM)`
			LIBS=`pkg-config --libs vchan-$(BACKEND_VMM)` -lqrexec-utils

Add qrexec back, use qubes-utils libraries for common code 2013-03-20 05:24:17 +00:00
			`all: qrexec-daemon qrexec-client`
			`qrexec-daemon: qrexec-daemon.o`
			`$(CC) -pie -g -o qrexec-daemon qrexec-daemon.o $(LIBS)`
			`qrexec-client: qrexec-client.o`
Revert "qrexec: fix deadlock in qrexec-client" This reverts commit 79abec90386e5477949ab04e2f80b9970c88b41b. The problem will not be applicable in new protocol, where vchan connection is directly between VMs, so there is no longer two connected qrexec-clients - always one end of data flow in qrexec-client is vchan, which provide information about amount of data to read or buffer space to write (lack of the later in case of pipes was a cause of the original problem). 2014-09-09 22:12:18 +00:00			`$(CC) -pie -g -o qrexec-client qrexec-client.o $(LIBS)`
Add qrexec back, use qubes-utils libraries for common code 2013-03-20 05:24:17 +00:00			`clean:`
			`rm -f .o ~ qrexec-daemon qrexec-client`