minix/lib/libmthread/Makefile

# Makefile for libmthread

LIB=	mthread

SRCS=	\
	allocate.c \
	attribute.c \
	mutex.c \
	event.c \
	rwlock.c \
	misc.c \
	queue.c \
	condition.c \
	scheduler.c \
	key.c

WARNS?=	4

.include <bsd.lib.mk>
Add libmthread and test59 to test the implementation 2010-09-21 14:22:38 +02:00			`# Makefile for libmthread`

			`LIB= mthread`

			`SRCS= \`
			`allocate.c \`
			`attribute.c \`
			`mutex.c \`
adding rwlock and event support to mthread 2011-11-29 14:03:49 +01:00			`event.c \`
			`rwlock.c \`
Add libmthread and test59 to test the implementation 2010-09-21 14:22:38 +02:00			`misc.c \`
			`queue.c \`
			`condition.c \`
libmthread: support for thread-local storage (keys/specifics) 2011-04-14 13:54:43 +02:00			`scheduler.c \`
			`key.c`
Add libmthread and test59 to test the implementation 2010-09-21 14:22:38 +02:00
fix a few more minix specific warnings . also disable stack protection feature for gcc, causes build errors for pkgsrc gcc on minix Change-Id: I1c6e2bcb4d948098d642543d7b2711284ee55c72 2013-08-26 18:43:05 +02:00			`WARNS?= 4`
Let the build system manage compilation flags Do not hardcode warning and optimisation flags, otherwise the main options (i.e. DBG, CPPFLAGS) will not work as expected. You can still provide specific default by using DBG?=<value>. Doing so leaves the opportunity to override the setting from the commandline, while the default value from the build system is then ignored for that particular package. When crosscompiling, and using build.sh, adding -V DBG=<value> has this same effect as make DBG=<value>. Change-Id: Ic610e4d33b945acad64571e1431f1814291e2d84 2013-02-27 17:53:12 +01:00
Add libmthread and test59 to test the implementation 2010-09-21 14:22:38 +02:00			`.include <bsd.lib.mk>`