view libpurple/protocols/jabber/JEPS @ 24332: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

0045: IN PROGRESS
	Multi-User Chat
0047: IN PROGRESS
	In-Band Bytestreams
0060: NEED
	Pub-Sub
0071: AWAITING FINAL SPEC
	XHTML-IM
0073: NEED
	Basic IM Protocol Suite
0080: NEED (Do we?)
	Geographic Location Information
0084: NEED
	User Avatars in Jabber
0085: NEED
	Chat State Notifications
0089: WATCH
	Generic Alerts
0093: NEED
	Roster Item Exchange
0100: NEED
	Gateway Interaction (Transports)
0115: WATCH
	Client Capabilities
0117: NEED
	Intermediate IM Protocol Suite