2008-01-28 02:12:20 +00:00
|
|
|
AUTOMAKE_OPTIONS = gnu
|
2011-09-08 19:59:05 +00:00
|
|
|
EXTRA_DIST = autogen.sh ceph.spec.in ceph.spec
|
Use Google Test framework for unit tests.
Use ``make check`` to run the tests.
The src/gtest directory comes from ``svn export
http://googletest.googlecode.com/svn/tags/release-1.5.0 src/gtest``
and running "git add -f src/gtest".
gtest is licensed under the New BSD license, see src/gtest/COPYING.
For more on Google Test, see http://code.google.com/p/googletest/
Changed autogen.sh regenerate gtest automake files too. Make sure to
run ``./autogen.sh && ./configure`` after merging this commit, or
incremental builds may fail. The automake integration is inspired
heavily by the protobuf project, and may still be problematic.
Make git ignore files generated by gtest compilation.
Currently putting in just one new-style unit test, refactoring old
tests to fit will come in separate commits.
Note: if you are starting daemons, listening on TCP ports, using
multiple machines, mounting filesystems, etc, it's not a unit test
and does not belong in this setup. A framework for system/integration
tests will be provided later.
2011-01-07 21:15:40 +00:00
|
|
|
# the "." here makes sure check-local builds gtest before it is used
|
2011-06-14 19:53:33 +00:00
|
|
|
SUBDIRS = . src man
|
Use Google Test framework for unit tests.
Use ``make check`` to run the tests.
The src/gtest directory comes from ``svn export
http://googletest.googlecode.com/svn/tags/release-1.5.0 src/gtest``
and running "git add -f src/gtest".
gtest is licensed under the New BSD license, see src/gtest/COPYING.
For more on Google Test, see http://code.google.com/p/googletest/
Changed autogen.sh regenerate gtest automake files too. Make sure to
run ``./autogen.sh && ./configure`` after merging this commit, or
incremental builds may fail. The automake integration is inspired
heavily by the protobuf project, and may still be problematic.
Make git ignore files generated by gtest compilation.
Currently putting in just one new-style unit test, refactoring old
tests to fit will come in separate commits.
Note: if you are starting daemons, listening on TCP ports, using
multiple machines, mounting filesystems, etc, it's not a unit test
and does not belong in this setup. A framework for system/integration
tests will be provided later.
2011-01-07 21:15:40 +00:00
|
|
|
|
2011-01-13 21:38:40 +00:00
|
|
|
EXTRA_DIST += \
|
|
|
|
|
src/test/run-cli-tests \
|
2011-01-14 18:33:31 +00:00
|
|
|
src/test/cli \
|
2011-03-08 00:03:08 +00:00
|
|
|
src/test/downloads \
|
|
|
|
|
udev/50-rbd.rules
|
2011-06-14 19:53:33 +00:00
|
|
|
|
2011-08-09 22:21:53 +00:00
|
|
|
|
|
|
|
|
all-local:
|
|
|
|
|
if WITH_DEBUG
|
|
|
|
|
# We need gtest to build the rados-api tests. We only build those in
|
|
|
|
|
# a debug build, though.
|
2011-08-21 23:38:01 +00:00
|
|
|
@cd src/gtest && $(MAKE) $(AM_MAKEFLAGS) lib/libgtest.la lib/libgtest_main.la lib/libgtest.a lib/libgtest_main.a
|
2011-08-09 22:21:53 +00:00
|
|
|
endif
|
Use Google Test framework for unit tests.
Use ``make check`` to run the tests.
The src/gtest directory comes from ``svn export
http://googletest.googlecode.com/svn/tags/release-1.5.0 src/gtest``
and running "git add -f src/gtest".
gtest is licensed under the New BSD license, see src/gtest/COPYING.
For more on Google Test, see http://code.google.com/p/googletest/
Changed autogen.sh regenerate gtest automake files too. Make sure to
run ``./autogen.sh && ./configure`` after merging this commit, or
incremental builds may fail. The automake integration is inspired
heavily by the protobuf project, and may still be problematic.
Make git ignore files generated by gtest compilation.
Currently putting in just one new-style unit test, refactoring old
tests to fit will come in separate commits.
Note: if you are starting daemons, listening on TCP ports, using
multiple machines, mounting filesystems, etc, it's not a unit test
and does not belong in this setup. A framework for system/integration
tests will be provided later.
2011-01-07 21:15:40 +00:00
|
|
|
|
2011-08-09 22:21:53 +00:00
|
|
|
check-local:
|
|
|
|
|
# We build gtest this way, instead of using SUBDIRS, because with that,
|
|
|
|
|
# gtest's own tests would be run and that would slow us down.
|
|
|
|
|
@cd src/gtest && $(MAKE) $(AM_MAKEFLAGS) lib/libgtest.la lib/libgtest_main.la
|
2011-01-12 00:43:46 +00:00
|
|
|
# exercise cli tools
|
2011-01-13 20:59:11 +00:00
|
|
|
$(srcdir)/src/test/run-cli-tests '$(top_builddir)/src/test'
|
2011-01-12 00:43:46 +00:00
|
|
|
|
Use Google Test framework for unit tests.
Use ``make check`` to run the tests.
The src/gtest directory comes from ``svn export
http://googletest.googlecode.com/svn/tags/release-1.5.0 src/gtest``
and running "git add -f src/gtest".
gtest is licensed under the New BSD license, see src/gtest/COPYING.
For more on Google Test, see http://code.google.com/p/googletest/
Changed autogen.sh regenerate gtest automake files too. Make sure to
run ``./autogen.sh && ./configure`` after merging this commit, or
incremental builds may fail. The automake integration is inspired
heavily by the protobuf project, and may still be problematic.
Make git ignore files generated by gtest compilation.
Currently putting in just one new-style unit test, refactoring old
tests to fit will come in separate commits.
Note: if you are starting daemons, listening on TCP ports, using
multiple machines, mounting filesystems, etc, it's not a unit test
and does not belong in this setup. A framework for system/integration
tests will be provided later.
2011-01-07 21:15:40 +00:00
|
|
|
# "make distclean" both runs this and recurses into src/gtest, if
|
|
|
|
|
# gtest is in DIST_SUBDIRS. Take extra care to not fail when
|
|
|
|
|
# effectively cleaned twice.
|
|
|
|
|
clean-local:
|
|
|
|
|
@if test -e src/gtest/Makefile; then \
|
|
|
|
|
echo "Making clean in src/gtest"; \
|
|
|
|
|
cd src/gtest && $(MAKE) $(AM_MAKEFLAGS) clean; \
|
|
|
|
|
fi
|
2011-01-14 18:35:20 +00:00
|
|
|
|
|
|
|
|
@rm -rf src/test/virtualenv
|
