view libpurple/plugins/mono/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

SUBDIRS = api loader

mono_sources = GetBuddyBack.cs \
			   MPlugin.cs

EXTRA_DIST = $(mono_sources)

monodir = $(libdir)/purple-$(PURPLE_MAJOR_VERSION)
mono_SCRIPTS = MPlugin.dll GetBuddyBack.dll
mono_build_sources = $(addprefix $(srcdir)/, $(mono_sources))

all: $(mono_SCRIPTS)

SUFFIXES = .cs .dll
.cs.dll: api/PurpleAPI.dll $(mono_build_sources)
	mcs -t:library -lib:./api -out:$@ -r:PurpleAPI.dll $<

clean-local:
	rm -f $(mono_SCRIPTS)