minix/lib/libgpio/Makefile

# Makefile for libgpio

CPPFLAGS+= -D_SYSTEM

LIB=	gpio

SRCS=	\
	gpio_omap.c  clkconf.c

WARNS?=	5

.include <bsd.lib.mk>
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			`# Makefile for libgpio`
GPIO:further development * Generalize GPIO handling. * Add libs to configure gpio's clocks and pads * Add Interrupt handling. * Introduce mmio.h and log.h Change-Id: I928e4c807d15031de2eede4b3ecff62df795f8ac 2013-02-06 15:46:21 +01:00
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			`CPPFLAGS+= -D_SYSTEM`
GPIO:further development * Generalize GPIO handling. * Add libs to configure gpio's clocks and pads * Add Interrupt handling. * Introduce mmio.h and log.h Change-Id: I928e4c807d15031de2eede4b3ecff62df795f8ac 2013-02-06 15:46:21 +01:00
			`LIB= gpio`

			`SRCS= \`
			`gpio_omap.c clkconf.c`

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			`WARNS?= 5`

GPIO:further development * Generalize GPIO handling. * Add libs to configure gpio's clocks and pads * Add Interrupt handling. * Introduce mmio.h and log.h Change-Id: I928e4c807d15031de2eede4b3ecff62df795f8ac 2013-02-06 15:46:21 +01:00			`.include <bsd.lib.mk>`