view libpurple/purple-send-async @ 16906:b93b9994dc2f

Fix some compiler warnings. I don't see any reason we need to define VERSION on the GCC command line here. In file included from ../../libpurple/internal.h:29, from gntgf.c:22: ../../config.h:383:1: warning: "VERSION" redefined <command line>:1:1: warning: this is the location of the previous definition In file included from ../../libpurple/internal.h:29, from gnthistory.c:23: ../../config.h:383:1: warning: "VERSION" redefined <command line>:1:1: warning: this is the location of the previous definition In file included from ../../libpurple/internal.h:29, from lastlog.c:24: ../../config.h:383:1: warning: "VERSION" redefined <command line>:1:1: warning: this is the location of the previous definition

#!/bin/bash

METHOD_NAME=$1

if test -z "$METHOD_NAME" 
then
    cat <<EOF 
This program calls purple API functions using DBus.  As opposed to purple-send, 
it does not print the return value.

Usage:

   $0 method-name type1:parameter1 type2:parameter2 ...

This shell script just invokes dbus-send, see man dbus-send for how 
to specify the parameters.  

Examples:

   $0 PurpleCoreQuit

Use dbus-viewer to get the list of supported functions and their parameters.
EOF
    exit 1
fi

shift
dbus-send --dest=im.pidgin.purple.PurpleService --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@"

echo