rdo/Makefile

CFLAGS = -Wall -Wextra -Werror -Wl,-z,now
CFLAGS_RELEASE = ${CFLAGS} -O2 -s -D_FORTIFY_SOURCE=2
CFLAGS_DEBUG = ${CFLAGS} -O0 -g -fsanitize=undefined
CFLAGS_STATIC = ${CFLAGS_RELEASE} -static-pie
LIBS = -lcrypt
CC = gcc

all: rdo.c
	${CC} ${CFLAGS_RELEASE} rdo.c -o rdo ${LIBS}

static: rdo.c
	${CC} ${CFLAGS_STATIC} rdo.c -o rdo ${LIBS}

debug: rdo.c
	${CC} ${CFLAGS_DEBUG} rdo.c -o rdo ${LIBS}

install: rdo
	cp rdo /usr/bin/rdo
	chown root:root /usr/bin/rdo
	chmod 755 /usr/bin/rdo
	chmod u+s /usr/bin/rdo
	cp rdo_sample.conf /etc/rdo.conf
	chmod 600 /etc/rdo.conf

uninstall:
	rm /usr/bin/rdo
	rm /etc/rdo.conf

clean:
	rm rdo
Fix debug build GCC doesnt want to compile a binary with fortify when optimizations are disabled, so we move the fortification process into the release flags. 2022-03-08 16:26:18 +01:00			`CFLAGS = -Wall -Wextra -Werror -Wl,-z,now`
			`CFLAGS_RELEASE = ${CFLAGS} -O2 -s -D_FORTIFY_SOURCE=2`
Remove LSAN from the debug build For some unknown reason LSAN catches a SIGSEGV (rdo.c:45) when enabled, but removing it also removes the supposed SIGSEGV it catches. To repro, build the earlier build with LSAN, and enter a file that doesnt exist. As long as I don't know why LSAN thinks this simple error message causes a segmentation fault, I will remove it. 2022-03-08 16:44:46 +01:00			`CFLAGS_DEBUG = ${CFLAGS} -O0 -g -fsanitize=undefined`
Replace `--static` flag with `-static-pie` 2022-12-04 08:03:31 -03:00			`CFLAGS_STATIC = ${CFLAGS_RELEASE} -static-pie`
Add own readpassphrase function This removes the libbsd dependency. Fixed #10. 2022-05-05 08:21:48 +02:00			`LIBS = -lcrypt`
Refactor Makefile These changes make rdo build on my rpi, probably because this specific GCC version requires arguments in the order we now supply. We also disable ASAN in the debug build (for now), as it seems to cause a segfault on my rpi. 2022-02-09 19:37:43 +01:00			`CC = gcc`

Various Makefile additions We now have a normal and a debug build, both of which have full RELRO, appropriate handling of warnings and the default build has D_FORTIFY_SOURCE set to 2. 2021-07-14 06:13:34 +02:00			`all: rdo.c`
Refactor Makefile These changes make rdo build on my rpi, probably because this specific GCC version requires arguments in the order we now supply. We also disable ASAN in the debug build (for now), as it seems to cause a segfault on my rpi. 2022-02-09 19:37:43 +01:00			`${CC} ${CFLAGS_RELEASE} rdo.c -o rdo ${LIBS}`
Various Makefile additions We now have a normal and a debug build, both of which have full RELRO, appropriate handling of warnings and the default build has D_FORTIFY_SOURCE set to 2. 2021-07-14 06:13:34 +02:00
Add static compilation rule to makefile 2022-12-03 18:50:41 -03:00			`static: rdo.c`
			`${CC} ${CFLAGS_STATIC} rdo.c -o rdo ${LIBS}`

Various Makefile additions We now have a normal and a debug build, both of which have full RELRO, appropriate handling of warnings and the default build has D_FORTIFY_SOURCE set to 2. 2021-07-14 06:13:34 +02:00			`debug: rdo.c`
Refactor Makefile These changes make rdo build on my rpi, probably because this specific GCC version requires arguments in the order we now supply. We also disable ASAN in the debug build (for now), as it seems to cause a segfault on my rpi. 2022-02-09 19:37:43 +01:00			`${CC} ${CFLAGS_DEBUG} rdo.c -o rdo ${LIBS}`
First Commit 2021-07-13 21:33:12 +02:00
			`install: rdo`
			`cp rdo /usr/bin/rdo`
			`chown root:root /usr/bin/rdo`
			`chmod 755 /usr/bin/rdo`
			`chmod u+s /usr/bin/rdo`
Add config for rdo This is needed for #1. 2021-07-13 23:21:34 +02:00			`cp rdo_sample.conf /etc/rdo.conf`
Tighten permissions for the config file 2022-02-09 19:48:32 +01:00			`chmod 600 /etc/rdo.conf`
First Commit 2021-07-13 21:33:12 +02:00
			`uninstall:`
			`rm /usr/bin/rdo`
Add config for rdo This is needed for #1. 2021-07-13 23:21:34 +02:00			`rm /etc/rdo.conf`

First Commit 2021-07-13 21:33:12 +02:00			`clean:`
			`rm rdo`