The attached patch 1) adds lm-sha.h to libloudmouthinclude_HEADERS 2) #includes lm-sha.h in loudmouth.h
This makes it practical for applications to use Loudmouth's SHA1 code. By the way, was there any particular reason not to make lm_sha_hash reentrant (i.e. return char * rather than const gchar *)? -- Dafydd
diff -ur loudmouth-1.1.4/loudmouth/loudmouth.h loudmouth-1.1.4.patched/loudmouth/loudmouth.h --- loudmouth-1.1.4/loudmouth/loudmouth.h 2004-10-22 00:18:51.000000000 +0100 +++ loudmouth-1.1.4.patched/loudmouth/loudmouth.h 2006-10-15 00:34:48.000000000 +0100 @@ -30,6 +30,7 @@ #include <loudmouth/lm-message-node.h> #include <loudmouth/lm-proxy.h> #include <loudmouth/lm-utils.h> +#include <loudmouth/lm-sha.h> #include <loudmouth/lm-ssl.h> #undef LM_INSIDE_LOUDMOUTH_H diff -ur loudmouth-1.1.4/loudmouth/Makefile.am loudmouth-1.1.4.patched/loudmouth/Makefile.am --- loudmouth-1.1.4/loudmouth/Makefile.am 2006-09-08 14:00:58.000000000 +0100 +++ loudmouth-1.1.4.patched/loudmouth/Makefile.am 2006-10-15 00:36:22.000000000 +0100 @@ -55,6 +55,7 @@ lm-message-node.h \ lm-utils.h \ lm-proxy.h \ + lm-sha.h \ lm-ssl.h \ loudmouth.h \ $(NULL)
