freebsd-nq/config/Rules.am

###############################################################################
# Copyright (C) 2007-2010 Lawrence Livermore National Security, LLC.
# Copyright (C) 2007 The Regents of the University of California.
# Written by Brian Behlendorf <behlendorf1@llnl.gov>.
###############################################################################
# Common rules for user space components.
###############################################################################

DEFAULT_INCLUDES = -include ${top_builddir}/spl_config.h

AM_LIBTOOLFLAGS = --silent
AM_CPPFLAGS = -D__USE_LARGEFILE64
AM_CFLAGS  = -Wall -Wshadow -Wstrict-prototypes -fno-strict-aliasing
AM_CFLAGS += ${DEBUG_CFLAGS}
Public Release Prep Updated AUTHORS, COPYING, DISCLAIMER, and INSTALL files. Added standardized headers to all source file to clearly indicate the copyright, license, and to give credit where credit is due. 2010-05-17 15:18:00 -07:00			`###############################################################################`
			`# Copyright (C) 2007-2010 Lawrence Livermore National Security, LLC.`
			`# Copyright (C) 2007 The Regents of the University of California.`
			`# Written by Brian Behlendorf <behlendorf1@llnl.gov>.`
			`###############################################################################`
			`# Common rules for user space components.`
			`###############################################################################`

Support custom build directories One of the neat tricks an autoconf style project is capable of is allow configurion/building in a directory other than the source directory. The major advantage to this is that you can build the project various different ways while making changes in a single source tree. For example, this project is designed to work on various different Linux distributions each of which work slightly differently. This means that changes need to verified on each of those supported distributions perferably before the change is committed to the public git repo. Using nfs and custom build directories makes this much easier. I now have a single source tree in nfs mounted on several different systems each running a supported distribution. When I make a change to the source base I suspect may break things I can concurrently build from the same source on all the systems each in their own subdirectory. wget -c http://github.com/downloads/behlendorf/spl/spl-x.y.z.tar.gz tar -xzf spl-x.y.z.tar.gz cd spl-x-y-z ------------------------- run concurrently ---------------------- <ubuntu system> <fedora system> <debian system> <rhel6 system> mkdir ubuntu mkdir fedora mkdir debian mkdir rhel6 cd ubuntu cd fedora cd debian cd rhel6 ../configure ../configure ../configure ../configure make make make make make check make check make check make check This is something the project has almost supported for a long time but finishing this support should save me lots of time. 2010-09-02 12:12:39 -07:00			`DEFAULT_INCLUDES = -include ${top_builddir}/spl_config.h`
Build system update - Added default build flags: -Wall -Wstrict-prototypes -Werror -Wshadow - Added missing Makefile's for include/ subdirectories. 2009-02-12 14:45:22 -08: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 15:21:06 -07:00			`AM_LIBTOOLFLAGS = --silent`
build: use CPPFLAGS -D and -I are preprocessor flags, so should preferably be in the appropriate variable. Signed-off-by: Jan Engelhardt <jengelh@inai.de> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2013-03-30 03:30:25 +01:00			`AM_CPPFLAGS = -D__USE_LARGEFILE64`
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-06-30 17:05:36 -07:00			`AM_CFLAGS = -Wall -Wshadow -Wstrict-prototypes -fno-strict-aliasing`
build: use CPPFLAGS -D and -I are preprocessor flags, so should preferably be in the appropriate variable. Signed-off-by: Jan Engelhardt <jengelh@inai.de> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2013-03-30 03:30:25 +01:00			`AM_CFLAGS += ${DEBUG_CFLAGS}`