view src/protocols/oscar/meta.c @ 4070:6efe00ee7de8

[gaim-migrate @ 4282] Just shuffling around some version stuff. I'm planning on changing things to be aim 5.1ish, but I want to do it in a separate patch, so it will be easy to unpatch if there are problems. Also, I figured out what those PleaseUpgrade000 buddies are. Like, if you add "[e-mail]" to your buddy list, then sign on with an aim client that advertises an old version of the ssi protocol (eg. gaim), then the server replaces "[e-mail]" with "PleaseUpgrade000" on the fly. It might replace other screen names, as well, I'm not exactly sure. Uh, so that problem should hopefully go away when I change the ssi family to 4, along with change other versions to be 5.1ish. Ribbit. committer: Tailor Script <[e-mail]>

/*
 * Administrative things for libfaim.
 *
 *  
 */

#define FAIM_INTERNAL
#include <aim.h>

#ifdef _WIN32
#include "win32dep.h"
#endif

faim_export char *aim_getbuilddate(void)
{
	return AIM_BUILDDATE;
}

faim_export char *aim_getbuildtime(void)
{
	return AIM_BUILDTIME;
}

faim_export int aim_getbuildstring(char *buf, int buflen)
{

	snprintf(buf, buflen, "%d.%d.%d-%s%s", 
			FAIM_VERSION_MAJOR,
			FAIM_VERSION_MINOR,
			FAIM_VERSION_MINORMINOR,
			aim_getbuilddate(),
			aim_getbuildtime());

	return 0;
}

faim_internal void faimdprintf(aim_session_t *sess, int dlevel, const char *format, ...)
{
	if (!sess) {
		fprintf(stderr, "faimdprintf: no session! boo! (%d, %s)\n", dlevel, format);
		return;
	}

	if ((dlevel <= sess->debug) && sess->debugcb) {
		va_list ap;

		va_start(ap, format);
		sess->debugcb(sess, dlevel, format, ap);
		va_end(ap);
	}

	return;
}