Mercurial > pidgin

view libpurple/tests/Makefile.am @ 28788:5152c6cea318

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Make sure libpurple libraries are the first thing in the test suite's library path. Maybe the newer libtool's don't leave out the system library path when constructing this now, but if the system path is first, running the tests will load the system version of libpurple instead of the just built copy. Fixes #10966.
author Elliott Sales de Andrade <qulogic@pidgin.im>
date Sun, 13 Dec 2009 02:27:48 +0000
parents 338eeaf371e2
children 485f69e04d6a
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_jabber_scram.c \
		test_qq.c \
		test_yahoo_util.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=\
		$(top_builddir)/libpurple/protocols/jabber/libjabber.la \
		$(top_builddir)/libpurple/protocols/qq/libqq.la \
		$(top_builddir)/libpurple/protocols/yahoo/libymsg.la \
		$(top_builddir)/libpurple/libpurple.la \
        @CHECK_LIBS@ \
		$(GLIB_LIBS)

endif