summaryrefslogtreecommitdiff
path: root/Makefile.am
Commit message (Collapse)AuthorAgeFilesLines
* debian: add udev rulesSamuel Just2011-03-101-1/+2
| | | | | | Add /lib/udev/rules.d/50-rbd.rules to debian package. Signed-off-by: Samuel Just <samuel.just@dreamhost.com>
* workunits: add direct_io_testColin Patrick McCabe2011-01-201-2/+1
| | | | Signed-off-by: Colin McCabe <colin.mccabe@dreamhost.com>
* Clean up test virtualenv on "make clean".Tommi Virtanen2011-01-141-0/+2
| | | | Found by "make distcheck".
* Include the cli tests in a dist tarball.Tommi Virtanen2011-01-141-0/+1
| | | | Found by "make distcheck".
* Also distribute pre-downloaded tarballs.Tommi Virtanen2011-01-141-1/+3
| | | | Found by "make distcheck".
* Teach run-cli-tests about build dirs.Tommi Virtanen2011-01-141-1/+1
| | | | | | | | | 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".
* run-cli-tests is in srcdir not in build dir.Tommi Virtanen2011-01-141-2/+1
| | | | Found by "make distcheck".
* Include run-cli-tests in release tarball.Tommi Virtanen2011-01-141-0/+1
| | | | Found by "make distcheck".
* Fix confusing comment about gtest automake hookup.Tommi Virtanen2011-01-131-3/+3
|
* Add CLI tests for osdmaptool and friends.Tommi Virtanen2011-01-111-2/+7
| | | | | | | | | | 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.
* Use Google Test framework for unit tests.Tommi Virtanen2011-01-101-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Makefile: drop unnecessary dist-hook for make_versionSage Weil2010-07-061-2/+0
| | | | Signed-off-by: Sage Weil <sage@newdream.net>
* debian: put debian/ in .diff.gz, not release tarballSage Weil2010-03-111-1/+1
|
* Makefile: include debian/Sage Weil2010-02-281-1/+1
|
* debian: updated debian build scripts, changelogSage Weil2010-02-081-1/+1
|
* man: mkcephfs, cosd man pagesSage Weil2009-03-101-1/+1
|
* ceph_ver: show the git sha1 version in the logsYehuda Sadeh2009-03-031-0/+3
|
* v0.6v0.6Sage Weil2009-01-201-1/+1
|
* debian: fix debian-doc; include debian dir in dist tarballSage Weil2008-10-091-2/+2
|
* no more m4Sage Weil2008-07-111-2/+1
|
* getting closer to building swig stuffSage Weil2008-03-121-1/+2
|
* more automake. make dist seems to workSage Weil2008-01-281-1/+1
|
* more automake funSage Weil2008-01-281-1/+1
|
* first pass at autoconf and automakeSage Weil2008-01-271-0/+3