summaryrefslogtreecommitdiff
path: root/autogen.sh
Commit message (Collapse)AuthorAgeFilesLines
* Use Google Test framework for unit tests.Tommi Virtanen2011-01-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* autogen.sh: check for pkg-configColin Patrick McCabe2010-11-051-0/+13
| | | | | | | To avoid seeing confusing errors later in the configure process, in autogen.sh, check to make sure the pkg-config program is installed. Signed-off-by: Colin McCabe <colinm@hq.newdream.net>
* automake: some clean upSage Weil2010-05-181-1/+1
|
* rados: build librados, libcrush using libtoolSage Weil2009-05-111-0/+1
| | | | Finally?
* no more m4 dirSage Weil2008-07-111-1/+1
|
* libcrushwrapper.so now builds, yaySage Weil2008-03-121-1/+0
|
* getting closer to building swig stuffSage Weil2008-03-121-1/+2
|
* autogen.shSage Weil2008-01-281-0/+7