minix/lib/libgpio/Makefile

# Makefile for libgpio

CPPFLAGS+= -D_SYSTEM

LIB=	gpio

SRCS=	\
	gpio_omap.c

WARNS?=	5

CFLAGS+= -fno-builtin

.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= \`
clkconf: move clkconf from libgpio to it's own lib Clock configuration will be needed by other/future subsystems such as i2c. Extract the functionality from libgpio and put it into it's own library. Change-Id: I6f6de0b3fb4d305ddfeac74123b78c983d1318dd 2013-06-17 14:23:31 +02:00			`gpio_omap.c`
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			`WARNS?= 5`

Synchronize on NetBSD-CVS (2013/12/1 12:00:00 UTC) - Fix for possible unset uid/gid in toproto - Fix for default mtree style - Update libelf - Importing libexecinfo - Resynchronize GCC, mpc, gmp, mpfr - build.sh: Replace params with show-params. This has been done as the make target has been renamed in the same way, while a new target named params has been added. This new target generates a file containing all the parameters, instead of printing it on the console. - Update test48 with new etc/services (Fix by Ben Gras <ben@minix3.org) get getservbyport() out of the inner loop Change-Id: Ie6ad5226fa2621ff9f0dee8782ea48f9443d2091 2013-12-06 12:04:52 +01:00			`CFLAGS+= -fno-builtin`

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>`