RepoMirrors
/
ceph
mirror of https://github.com/ceph/ceph
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ceph/Makefile.am

29 lines
931 B
Makefile
Raw Normal View History

first pass at autoconf and automake
2008-01-28 02:12:20 +00:00
AUTOMAKE_OPTIONS = gnu
debian: put debian/ in .diff.gz, not release tarball
2010-03-10 05:38:30 +00:00
EXTRA_DIST = autogen.sh ceph.spec.in
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
SUBDIRS = . src man
ceph_ver: show the git sha1 version in the logs
2009-03-03 23:32:20 +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
Also distribute pre-downloaded tarballs. Found by "make distcheck".
2011-01-13 21:38:40 +00:00
EXTRA_DIST += \
src/test/run-cli-tests \
Include the cli tests in a dist tarball. Found by "make distcheck".
2011-01-14 18:33:31 +00:00
src/test/cli \
Also distribute pre-downloaded tarballs. Found by "make distcheck".
2011-01-13 21:38:40 +00:00
src/test/downloads
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
check-local:
Fix confusing comment about gtest automake hookup.
2011-01-13 19:32:16 +00:00
# Build gtest before we build our own tests. Doing this instead
# of SUBDIRS because with that, gtest's own tests would be run
# and that would slow us down.
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
@echo "Making lib/libgtest.a lib/libgtest_main.a in src/gtest"
@cd src/gtest && $(MAKE) $(AM_MAKEFLAGS) lib/libgtest.la lib/libgtest_main.la
Add CLI tests for osdmaptool and friends. Uses a python package "cram" as test runner. Requires PIP (python-pip.deb) installed on the build machine, to actually run these tests. The cram application itself is included as a tarball that gets installed in a virtualenv when the tests are run. cram is GPL.
2011-01-12 00:43:46 +00:00
# exercise cli tools
Teach run-cli-tests about build dirs. An optional argument points can tell it where to put generated files (in this case, virtualenv). Provide the argument in Makefile.am. Options are still passed to cram, so you can say "./src/test/run-cli-tests -i".
2011-01-13 20:59:11 +00:00
$(srcdir)/src/test/run-cli-tests '$(top_builddir)/src/test'
Add CLI tests for osdmaptool and friends. Uses a python package "cram" as test runner. Requires PIP (python-pip.deb) installed on the build machine, to actually run these tests. The cram application itself is included as a tarball that gets installed in a virtualenv when the tests are run. cram is GPL.
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