view libpurple/tests/Makefile.am @ 24389:2b62300d2c19

Use libtool to build static archives when --with-static-prpls is passed to configure. Does anyone know why we weren't using libtool before? We were building old-fashioned .a files. But libtool archives (.la) can contain either static or shared libraries. I found it a lot easier to get static prpl compilation working after making this change (that is to say, it worked). Without this I got this error, which is probably fixable, but consistently using libtool seems like it makes things easier: *** Warning: Linking the shared library libpurple.la against the *** static library ../libpurple/protocols/msn/libmsn.a is not portable! /usr/bin/ld: ../libpurple/protocols/msn/libmsn.a(libmsn_a-msn.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../libpurple/protocols/msn/libmsn.a: could not read symbols: Bad value collect2: ld returned 1 exit status

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) \
		-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