Mercurial > pidgin.yaz

view libpurple/plugins/mono/loader/Makefile.am @ 30288:a81d44a11d99

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
If SASL authentication fails, we generally shouldn't be setting an error message, as the actual error was communicated via the "urn:ietf:params:xml:ns:xmpp-sasl" failure stanza. Setting an error means that jabber_auth_handle_failure() won't ever call jabber_parse_error() to extract the actual error message and interpretation. For example, if authentication fails, previously we would show "SASL authentication failed" and think it was a PURPLE_CONNECTION_ERROR_NETWORK_ERROR which is incorrect. Now, jabber_parse_error() gets a chance to return "Not Authorized", clear the saved password, and return PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. We should still set this error message if there is an internal SASL failure leading to SASL_BADPARAM or SASL_NOMEM.
author Evan Schoenberg <evan.s@dreskin.net>
date Tue, 04 May 2010 01:46:40 +0000
parents 0dcd915899ae
children
line wrap: on
line source

plugindir = $(libdir)/purple-$(PURPLE_MAJOR_VERSION)

plugin_LTLIBRARIES = mono.la

mono_la_SOURCES	= \
	mono.c \
	mono-glue.h \
	mono-helper.c \
	mono-helper.h \
	debug-glue.c \
	signal-glue.c \
	blist-glue.c \
	status-glue.c 

mono_la_LDFLAGS  = -module -avoid-version

mono_la_LIBADD = $(MONO_LIBS)

AM_CPPFLAGS = \
	-I$(top_srcdir) \
	-I$(top_srcdir)/libpurple \
	$(DEBUG_CFLAGS) \
	$(PLUGIN_CFLAGS) \
	$(MONO_CFLAGS)