comparison libpurple/protocols/null/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
author Mark Doliner <mark@kingant.net>
date Wed, 12 Nov 2008 11:30:51 +0000
parents afee8b840d91
children
comparison
equal deleted inserted replaced
24388:7e8175f9b009 24389:2b62300d2c19
1 EXTRA_DIST = README Makefile.mingw 1 EXTRA_DIST = \
2 Makefile.mingw \
3 README
2 4
3 pkgdir = $(libdir)/purple-$(PURPLE_MAJOR_VERSION) 5 pkgdir = $(libdir)/purple-$(PURPLE_MAJOR_VERSION)
4 6
5 NULLSOURCES = nullprpl.c 7 NULLSOURCES = nullprpl.c
6 8
8 10
9 libnull_la_LDFLAGS = -module -avoid-version 11 libnull_la_LDFLAGS = -module -avoid-version
10 12
11 # nullprpl isn't built by default. when it is built, it's dynamically linked. 13 # nullprpl isn't built by default. when it is built, it's dynamically linked.
12 st = 14 st =
13 pkg_LTLIBRARIES = libnull.la 15 pkg_LTLIBRARIES = libnull.la
14 libnull_la_SOURCES = $(NULLSOURCES) 16 libnull_la_SOURCES = $(NULLSOURCES)
15 libnull_la_LIBADD = $(GLIB_LIBS) 17 libnull_la_LIBADD = $(GLIB_LIBS)
16 18
17 AM_CPPFLAGS = \ 19 AM_CPPFLAGS = \
18 -I$(top_srcdir)/libpurple \ 20 -I$(top_srcdir)/libpurple \