Mercurial > pidgin

view libpurple/tests/Makefile.am @ 27308:fc5508709e74

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Use glib's SHA1, SHA256, and MD5 implementations when available (glib 2.16) These SHA1 and SHA256 implementations do not expose any options, which the built-in ones do (for getting/setting sizeHi, sizeLo, and lenW). Nothing in Pidgin uses those (and I can't think of a decent use case), so I think this is OK. Feel free to disagree. As I mentioned on the mailing list, glib's SHA1 implementation was just under 3x as fast on my system.
author Paul Aurich <paul@darkrain42.org>
date Sat, 04 Jul 2009 23:13:23 +0000
parents b0f0579f5f22
children 42359a734696
line wrap: on
line source

if HAVE_CHECK
TESTS=check_libpurple

clean-local:
	-rm -rf libpurple..

check_PROGRAMS=check_libpurple

check_libpurple_SOURCES=\
        check_libpurple.c \
	    tests.h \
		test_cipher.c \
		test_jabber_jutil.c \
		test_util.c \
		$(top_builddir)/libpurple/util.h

check_libpurple_CFLAGS=\
        @CHECK_CFLAGS@ \
		$(GLIB_CFLAGS) \
		$(DEBUG_CFLAGS) \
		$(LIBXML_CFLAGS) \
		-I.. \
		-I$(top_srcdir)/libpurple \
		-DBUILDDIR=\"$(top_builddir)\"

check_libpurple_LDADD=\
        @CHECK_LIBS@ \
		$(GLIB_LIBS) \
		$(top_builddir)/libpurple/protocols/jabber/libjabber.la \
		$(top_builddir)/libpurple/libpurple.la

endif