qubes-core-admin-linux/qrexec/Makefile

CC=gcc
CFLAGS+=-I. -g -Wall -Wextra -Werror -pie -fPIC
XENLIBS=-lvchan -lxenstore -lxenctrl
LIBS=$(XENLIBS) -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) -lpthread
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`
Add -Wextra -Werror to all C compile flags 2014-02-16 09:29:22 +00:00			`CFLAGS+=-I. -g -Wall -Wextra -Werror -pie -fPIC`
Add qrexec back, use qubes-utils libraries for common code 2013-03-20 05:24:17 +00:00			`XENLIBS=-lvchan -lxenstore -lxenctrl`
			`LIBS=$(XENLIBS) -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`
qrexec: fix deadlock in qrexec-client When VM-VM qrexec service is called, two qrexec-clients are connected in dom0. If both VMs are sending data simultaneously it can happen that both qrexec-client processes will call write(2) and none of them will be reading -> deadlock. Solve it by handling I/O in two separate threads (one for reading from VM, another for writing), at any time qrexec-client is ready to accept data from either direction. 2014-07-01 01:24:46 +00:00			`$(CC) -pie -g -o qrexec-client qrexec-client.o $(LIBS) -lpthread`
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`