zfs/config/Rules.am

DEFAULT_INCLUDES = -include ${top_srcdir}/zfs_config.h

AM_LIBTOOLFLAGS = --silent
AM_CFLAGS  = -Wall -Wstrict-prototypes -fno-strict-aliasing ${DEBUG_CFLAGS}
AM_CFLAGS += -D_GNU_SOURCE -D__EXTENSIONS__ -D_REENTRANT
AM_CFLAGS += -D_POSIX_PTHREAD_SEMANTICS -D_FILE_OFFSET_BITS=64
AM_CFLAGS += -D_LARGEFILE64_SOURCE -DTEXT_DOMAIN=\"zfs-linux-user\"
Allow zfs_config.h to be included by dependant packages (updated) We need dependent packages to be able to include zfs_config.h to build properly. This was partially solved previously be using AH_BOTTOM to #undef common #defines (PACKAGE, VERSION, etc) which autoconf always adds and cannot be easily removed. This solution works as long as the zfs_config.h is included before your projects config.h. That turns out to be easier said than done. In particular, this is a problem when your package includes its config.h using the -include gcc option which ensures the first thing included is your config.h. To handle all cases cleanly I have removed the AH_BOTTOM hack and replaced it with an AC_CONFIG_HEADERS command. This command runs immediately after zfs_config.h is written and with a little awk-foo it strips the offending #defines from the file. This eliminates the problem entirely and makes header safe for inclusion. 2010-03-22 23:42:18 +00:00			`DEFAULT_INCLUDES = -include ${top_srcdir}/zfs_config.h`
Add DEFAULT_INCLUDE to rules, adjust = to += accordingly 2008-12-16 16:58:41 +00:00
Add support for 'make -s' silent builds The cleanest way to do this is to set AM_LIBTOOLFLAGS = --silent. However, AM_LIBTOOLFLAGS is not honored by automake-1.9.6-2.1 which is what I have been using. To cleanly handle this I am updating to automake-1.11-3 which is why it looks like there is a lot of churn in the Makefiles. 2010-03-26 22:41:41 +00:00			`AM_LIBTOOLFLAGS = --silent`
Only make compiler warnings fatal with --enable-debug While in theory I like the idea of compiler warnings always being fatal. In practice this causes problems when small harmless errors cause build failures for end users. To handle this I've updated the build system such that -Werror is only used when --enable-debug is passed to configure. This is how I always build when developing so I'll catch all build warnings and end users will not get stuck by minor issues. 2010-07-14 17:25:54 +00:00			`AM_CFLAGS = -Wall -Wstrict-prototypes -fno-strict-aliasing ${DEBUG_CFLAGS}`
Refine Makefiles 2008-12-12 18:57:05 +00:00			`AM_CFLAGS += -D_GNU_SOURCE -D__EXTENSIONS__ -D_REENTRANT`
Use AM_CFLAGS 2008-12-12 18:15:59 +00:00			`AM_CFLAGS += -D_POSIX_PTHREAD_SEMANTICS -D_FILE_OFFSET_BITS=64`
Refine Makefiles 2008-12-12 18:57:05 +00:00			`AM_CFLAGS += -D_LARGEFILE64_SOURCE -DTEXT_DOMAIN=\"zfs-linux-user\"`