2007-02-08 01:46:44 +08:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
set -e
|
2007-02-14 10:12:41 +08:00
|
|
|
set -v
|
2007-02-08 01:46:44 +08:00
|
|
|
|
|
|
|
# Make things clean.
|
|
|
|
|
2008-08-22 03:31:55 +08:00
|
|
|
test -n "$1" && RESULTS=$1 || RESULTS=results.log
|
2010-05-01 00:57:10 +08:00
|
|
|
: ${AUTOBUILD_INSTALL_ROOT=$HOME/builder}
|
2007-02-08 01:46:44 +08:00
|
|
|
|
2013-09-14 19:29:42 +08:00
|
|
|
# If run under the autobuilder, we must use --nodeps with rpmbuild;
|
|
|
|
# but this can lead to odd error diagnosis for normal development.
|
|
|
|
nodeps=
|
|
|
|
if test "${AUTOBUILD_COUNTER+set}"; then
|
|
|
|
nodeps=--nodeps
|
|
|
|
fi
|
|
|
|
|
2007-02-08 01:46:44 +08:00
|
|
|
test -f Makefile && make -k distclean || :
|
2007-02-14 10:12:41 +08:00
|
|
|
rm -rf coverage
|
2007-02-08 01:46:44 +08:00
|
|
|
|
2010-04-30 22:52:54 +08:00
|
|
|
rm -rf build
|
|
|
|
mkdir build
|
|
|
|
cd build
|
2007-02-08 01:46:44 +08:00
|
|
|
|
2011-03-22 23:40:35 +08:00
|
|
|
# Run with options not normally exercised by the rpm build, for
|
|
|
|
# more complete code coverage.
|
2010-04-30 22:52:54 +08:00
|
|
|
../autogen.sh --prefix="$AUTOBUILD_INSTALL_ROOT" \
|
build: add configure option to disable gnulib tests
The gnulib testsuite is relatively stable - the only times it is
likely to have a test change from pass to fail is on a gnulib
submodule update or a major system change (such as moving from
Fedora 18 to 19, or other large change to libc). While it is an
important test for end users on arbitrary machines (to make sure
that the portability glue works for their machine), it mostly
wastes time for development testing (as most developers aren't
making any of the major changes that would cause gnulib tests
to alter behavior). Thus, it pays to make the tests optional
at configure time, defaulting to off for development, on for
tarballs, with autobuilders requesting it to be on. It also
helps to allow a make-time override, via VIR_TEST_EXPENSIVE=[01]
(much the way automake sets up V=[01] for overriding the configure
time default of how verbose to be).
Automake has some pretty hard-coded magic with regards to the
TESTS variable; I had quite a job figuring out how to keep
'make distcheck' passing regardless of the configure option
setting in use, while still disabling the tests at runtime
when I did not configure them on and did not use the override
variable. Thankfully, we require GNU make, which lets me
hide some information from Automake's magic handling of TESTS.
* bootstrap.conf (bootstrap_epilogue): Munge gnulib test variable.
* configure.ac (--enable-expensive-tests): Add new enable switch.
(VIR_TEST_EXPENSIVE_DEFAULT, WITH_EXPENSIVE_TESTS): Set new
witnesses.
* gnulib/tests/Makefile.am (TESTS): Make tests conditional on
configure settings and the VIR_TEST_EXPENSIVE variable.
* tests/Makefile.am (TESTS_ENVIRONMENT): Expose VIR_TEST_EXPENSIVE
to all tests.
* autobuild.sh: Enable all tests during autobuilds.
* libvirt.spec.in (%configure): Likewise.
* mingw-libvirt.spec.in (%mingw_configure): Likewise.
* docs/hacking.html.in: Document the option.
* HACKING: Regenerate.
Signed-off-by: Eric Blake <eblake@redhat.com>
2013-07-31 21:18:58 +08:00
|
|
|
--enable-expensive-tests \
|
2007-03-09 05:32:18 +08:00
|
|
|
--enable-test-coverage \
|
2011-03-22 23:40:35 +08:00
|
|
|
--disable-nls \
|
2013-04-02 23:52:31 +08:00
|
|
|
--enable-werror \
|
|
|
|
--enable-static
|
2007-02-08 01:46:44 +08:00
|
|
|
|
2008-08-28 17:08:44 +08:00
|
|
|
# If the MAKEFLAGS envvar does not yet include a -j option,
|
|
|
|
# add -jN where N depends on the number of processors.
|
|
|
|
case $MAKEFLAGS in
|
|
|
|
*-j*) ;;
|
|
|
|
*) n=$(getconf _NPROCESSORS_ONLN 2> /dev/null)
|
|
|
|
test "$n" -gt 0 || n=1
|
|
|
|
n=$(expr $n + 1)
|
|
|
|
MAKEFLAGS="$MAKEFLAGS -j$n"
|
|
|
|
export MAKEFLAGS
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
|
2007-02-08 01:46:44 +08:00
|
|
|
make
|
|
|
|
make install
|
|
|
|
|
2010-06-04 11:07:09 +08:00
|
|
|
# set -o pipefail is a bashism; this use of exec is the POSIX alternative
|
|
|
|
exec 3>&1
|
|
|
|
st=$(
|
|
|
|
exec 4>&1 >&3
|
2010-12-11 06:30:56 +08:00
|
|
|
{ make check syntax-check 2>&1 3>&- 4>&-; echo $? >&4; } | tee "$RESULTS"
|
2010-06-04 11:07:09 +08:00
|
|
|
)
|
|
|
|
exec 3>&-
|
2010-11-18 01:38:59 +08:00
|
|
|
test "$st" = 0
|
2008-05-30 04:43:08 +08:00
|
|
|
test -x /usr/bin/lcov && make cov
|
2007-02-08 01:46:44 +08:00
|
|
|
|
|
|
|
rm -f *.tar.gz
|
|
|
|
make dist
|
|
|
|
|
2012-06-16 00:13:11 +08:00
|
|
|
if test -n "$AUTOBUILD_COUNTER" ; then
|
2008-10-10 19:33:10 +08:00
|
|
|
EXTRA_RELEASE=".auto$AUTOBUILD_COUNTER"
|
|
|
|
else
|
|
|
|
NOW=`date +"%s"`
|
|
|
|
EXTRA_RELEASE=".$USER$NOW"
|
|
|
|
fi
|
2008-09-05 20:03:45 +08:00
|
|
|
|
2012-06-16 00:13:11 +08:00
|
|
|
if test -f /usr/bin/rpmbuild ; then
|
2013-09-14 19:29:42 +08:00
|
|
|
rpmbuild $nodeps \
|
2008-09-05 20:03:45 +08:00
|
|
|
--define "extra_release $EXTRA_RELEASE" \
|
|
|
|
--define "_sourcedir `pwd`" \
|
|
|
|
-ba --clean libvirt.spec
|
|
|
|
fi
|
|
|
|
|
2012-06-16 00:13:11 +08:00
|
|
|
# Test mingw32 cross-compile
|
|
|
|
if test -x /usr/bin/i686-w64-mingw32-gcc ; then
|
2008-09-05 20:03:45 +08:00
|
|
|
make distclean
|
|
|
|
|
2013-05-17 20:29:12 +08:00
|
|
|
PKG_CONFIG_LIBDIR="/usr/i686-w64-mingw32/sys-root/mingw/lib/pkgconfig:/usr/i686-w64-mingw32/sys-root/mingw/share/pkgconfig" \
|
2012-06-16 00:13:11 +08:00
|
|
|
PKG_CONFIG_PATH="$AUTOBUILD_INSTALL_ROOT/i686-w64-mingw32/sys-root/mingw/lib/pkgconfig" \
|
|
|
|
CC="i686-w64-mingw32-gcc" \
|
2010-04-30 22:52:54 +08:00
|
|
|
../configure \
|
2012-06-16 00:13:11 +08:00
|
|
|
--build=$(uname -m)-w64-linux \
|
|
|
|
--host=i686-w64-mingw32 \
|
|
|
|
--prefix="$AUTOBUILD_INSTALL_ROOT/i686-w64-mingw32/sys-root/mingw" \
|
build: add configure option to disable gnulib tests
The gnulib testsuite is relatively stable - the only times it is
likely to have a test change from pass to fail is on a gnulib
submodule update or a major system change (such as moving from
Fedora 18 to 19, or other large change to libc). While it is an
important test for end users on arbitrary machines (to make sure
that the portability glue works for their machine), it mostly
wastes time for development testing (as most developers aren't
making any of the major changes that would cause gnulib tests
to alter behavior). Thus, it pays to make the tests optional
at configure time, defaulting to off for development, on for
tarballs, with autobuilders requesting it to be on. It also
helps to allow a make-time override, via VIR_TEST_EXPENSIVE=[01]
(much the way automake sets up V=[01] for overriding the configure
time default of how verbose to be).
Automake has some pretty hard-coded magic with regards to the
TESTS variable; I had quite a job figuring out how to keep
'make distcheck' passing regardless of the configure option
setting in use, while still disabling the tests at runtime
when I did not configure them on and did not use the override
variable. Thankfully, we require GNU make, which lets me
hide some information from Automake's magic handling of TESTS.
* bootstrap.conf (bootstrap_epilogue): Munge gnulib test variable.
* configure.ac (--enable-expensive-tests): Add new enable switch.
(VIR_TEST_EXPENSIVE_DEFAULT, WITH_EXPENSIVE_TESTS): Set new
witnesses.
* gnulib/tests/Makefile.am (TESTS): Make tests conditional on
configure settings and the VIR_TEST_EXPENSIVE variable.
* tests/Makefile.am (TESTS_ENVIRONMENT): Expose VIR_TEST_EXPENSIVE
to all tests.
* autobuild.sh: Enable all tests during autobuilds.
* libvirt.spec.in (%configure): Likewise.
* mingw-libvirt.spec.in (%mingw_configure): Likewise.
* docs/hacking.html.in: Document the option.
* HACKING: Regenerate.
Signed-off-by: Eric Blake <eblake@redhat.com>
2013-07-31 21:18:58 +08:00
|
|
|
--enable-expensive-tests \
|
2012-03-27 23:47:11 +08:00
|
|
|
--enable-werror \
|
2013-11-23 00:42:22 +08:00
|
|
|
--without-libvirtd
|
2008-09-05 20:03:45 +08:00
|
|
|
|
|
|
|
make
|
|
|
|
make install
|
|
|
|
|
2012-06-16 00:13:11 +08:00
|
|
|
fi
|
|
|
|
|
|
|
|
# Test mingw64 cross-compile
|
|
|
|
if test -x /usr/bin/x86_64-w64-mingw32-gcc ; then
|
|
|
|
make distclean
|
|
|
|
|
2013-05-17 20:29:12 +08:00
|
|
|
PKG_CONFIG_LIBDIR="/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig:/usr/x86_64-w64-mingw32/sys-root/mingw/share/pkgconfig" \
|
2012-06-16 00:13:11 +08:00
|
|
|
PKG_CONFIG_PATH="$AUTOBUILD_INSTALL_ROOT/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig" \
|
|
|
|
CC="x86_64-w64-mingw32-gcc" \
|
|
|
|
../configure \
|
|
|
|
--build=$(uname -m)-w64-linux \
|
|
|
|
--host=x86_64-w64-mingw32 \
|
|
|
|
--prefix="$AUTOBUILD_INSTALL_ROOT/x86_64-w64-mingw32/sys-root/mingw" \
|
build: add configure option to disable gnulib tests
The gnulib testsuite is relatively stable - the only times it is
likely to have a test change from pass to fail is on a gnulib
submodule update or a major system change (such as moving from
Fedora 18 to 19, or other large change to libc). While it is an
important test for end users on arbitrary machines (to make sure
that the portability glue works for their machine), it mostly
wastes time for development testing (as most developers aren't
making any of the major changes that would cause gnulib tests
to alter behavior). Thus, it pays to make the tests optional
at configure time, defaulting to off for development, on for
tarballs, with autobuilders requesting it to be on. It also
helps to allow a make-time override, via VIR_TEST_EXPENSIVE=[01]
(much the way automake sets up V=[01] for overriding the configure
time default of how verbose to be).
Automake has some pretty hard-coded magic with regards to the
TESTS variable; I had quite a job figuring out how to keep
'make distcheck' passing regardless of the configure option
setting in use, while still disabling the tests at runtime
when I did not configure them on and did not use the override
variable. Thankfully, we require GNU make, which lets me
hide some information from Automake's magic handling of TESTS.
* bootstrap.conf (bootstrap_epilogue): Munge gnulib test variable.
* configure.ac (--enable-expensive-tests): Add new enable switch.
(VIR_TEST_EXPENSIVE_DEFAULT, WITH_EXPENSIVE_TESTS): Set new
witnesses.
* gnulib/tests/Makefile.am (TESTS): Make tests conditional on
configure settings and the VIR_TEST_EXPENSIVE variable.
* tests/Makefile.am (TESTS_ENVIRONMENT): Expose VIR_TEST_EXPENSIVE
to all tests.
* autobuild.sh: Enable all tests during autobuilds.
* libvirt.spec.in (%configure): Likewise.
* mingw-libvirt.spec.in (%mingw_configure): Likewise.
* docs/hacking.html.in: Document the option.
* HACKING: Regenerate.
Signed-off-by: Eric Blake <eblake@redhat.com>
2013-07-31 21:18:58 +08:00
|
|
|
--enable-expensive-tests \
|
2012-06-16 00:13:11 +08:00
|
|
|
--enable-werror \
|
2013-11-23 00:42:22 +08:00
|
|
|
--without-libvirtd
|
2012-06-16 00:13:11 +08:00
|
|
|
|
|
|
|
make
|
|
|
|
make install
|
|
|
|
|
|
|
|
fi
|
|
|
|
|
2008-09-05 20:03:45 +08:00
|
|
|
|
2012-06-16 00:13:11 +08:00
|
|
|
if test -x /usr/bin/i686-w64-mingw32-gcc && test -x /usr/bin/x86_64-w64-mingw32-gcc ; then
|
|
|
|
if test -f /usr/bin/rpmbuild ; then
|
2013-09-14 19:29:42 +08:00
|
|
|
rpmbuild $nodeps \
|
2008-10-10 19:33:10 +08:00
|
|
|
--define "extra_release $EXTRA_RELEASE" \
|
|
|
|
--define "_sourcedir `pwd`" \
|
2012-06-16 00:13:11 +08:00
|
|
|
-ba --clean mingw-libvirt.spec
|
2008-10-10 19:33:10 +08:00
|
|
|
fi
|
2007-02-08 01:46:44 +08:00
|
|
|
fi
|