alphatau 0.1.0

data/ext/alphatau/native/sdl/visualtest/COPYING.txt

@@ -0,0 +1,18 @@
+Visual and Interactive Test Automation for SDL 2.0
+Copyright (C) 2013 Apoorv Upreti <apoorvupreti@gmail.com>
+
+This software is provided 'as-is', without any express or implied
+warranty.  In no event will the authors be held liable for any damages
+arising from the use of this software.
+
+Permission is granted to anyone to use this software for any purpose,
+including commercial applications, and to alter it and redistribute it
+freely, subject to the following restrictions:
+
+1. The origin of this software must not be misrepresented; you must not
+   claim that you wrote the original software. If you use this software
+   in a product, an acknowledgment in the product documentation would be
+   appreciated but is not required.
+2. Altered source versions must be plainly marked as such, and must not be
+   misrepresented as being the original software.
+3. This notice may not be removed or altered from any source distribution.

data/ext/alphatau/native/sdl/visualtest/Makefile.in

@@ -0,0 +1,37 @@
+# Makefile to build the SDL tests
+srcdir  = @srcdir@
+CC      = @CC@
+EXE	= @EXE@
+CFLAGS  = @CFLAGS@ -I../include -I./include
+LIBS	= @LIBS@
+TARGETS = \
+	testharness$(EXE) \
+	testquit$(EXE)
+all: Makefile $(TARGETS)
+Makefile: $(srcdir)/Makefile.in
+	$(SHELL) config.status $@
+testharness$(EXE): $(srcdir)/src/action_configparser.c \
+		   $(srcdir)/src/harness_argparser.c \
+		   $(srcdir)/src/rwhelper.c \
+		   $(srcdir)/src/testharness.c \
+		   $(srcdir)/src/variator_exhaustive.c \
+		   $(srcdir)/src/variators.c \
+		   $(srcdir)/src/screenshot.c \
+		   $(srcdir)/src/harness_argparser.c \
+		   $(srcdir)/src/sut_configparser.c \
+		   $(srcdir)/src/variator_common.c \
+		   $(srcdir)/src/variator_random.c \
+		   $(srcdir)/src/parsehelper.c \
+		   $(srcdir)/src/mischelper.c \
+		   $(srcdir)/src/linux/linux_process.c \
+		   $(srcdir)/src/windows/windows_process.c \
+		   $(srcdir)/src/windows/windows_screenshot.c
+	$(CC) -o $@ $^ $(CFLAGS) $(LIBS)
+testquit$(EXE): $(srcdir)/unittest/testquit.c
+	$(CC) -o $@ $^ $(CFLAGS) $(LIBS)
+clean:
+	rm -f $(TARGETS)
+distclean: clean
+	rm -f Makefile
+	rm -f config.status config.cache config.log
+	rm -rf $(srcdir)/autom4te*

data/ext/alphatau/native/sdl/visualtest/README.txt

@@ -0,0 +1,214 @@
+/*!
+
+\mainpage Visual and Interactive Test Automation for SDL 2.0
+
+\section license_sec License
+Check the file \c COPYING.txt for licensing information.
+
+\section intro_sec Introduction
+The goal of this GSoC project is to automate the testing of testsprite2.
+testsprite2 takes 26 parameters which have thousands of valid combinations and is
+used to validate SDL's window, mouse and rendering behaviour. By having a test
+harness that runs testsprite2 with various command line argument strings and
+validates the output for each run, we can make testing an easier task for
+maintainers, contributors and testers. The test harness can be used by a continuous
+integration system (like buildbot or jenkins) to validate SDL after checkins.
+
+SDL Homepage: http://libsdl.org/
+
+\section build_sec Building
+
+\subsection build_linux Building on Linux/Cygwin
+<tt>./autogen.sh; ./configure; make;</tt>
+
+\subsection build_windows Building on Windows
+Use the Visual Studio solution under \c SDL/VisualC/visualtest.
+
+\section docs_sec Documentation
+Documentation is available via Doxygen. To build the documentation, cd to the
+SDL/visualtest/docs directory and run \c doxygen. A good starting point for
+exploring the documentation is \c SDL/visualtest/docs/html/index.html
+
+\section usage_sec Usage
+To see all the options supported by the test harness, just run \c testharness
+with no arguments.
+
+At the moment the following options are supported:
+\li \c sutapp - Path to the system under test (SUT) application
+\li \c sutargs - Launch the SUT with the specified arguments string
+\li \c timeout - The maximum time after which the SUT process will be killed;
+	passed as hh:mm:ss; default 00:01:00
+\li \c variator - Which variator to use; see \ref variators_sec
+\li \c num-variations - The number of variations to run for; taken to be 
+	1 for the random variator and ALL for the exhaustive variator by default
+\li \c no-launch - Just print the arguments string for each variation without
+	launching the SUT or performing any actions
+\li \c parameter-config - A config file that describes the command line parameters
+	supported by the SUT; see \ref paramconfig_sec or the sample *.parameters files
+	for more details
+\li \c action-config - A config file with a list of actions to be performed while
+	the SUT is running; see \ref actionconfig_sec or the sample *.actions files
+\li \c output-dir - Path to the directory where screenshots should be saved; is
+	created if it doesn't exist; taken to be "./output" by default
+\li \c verify-dir - Path to the directory with the verification images; taken to 
+	be "./verify" by default
+
+Paths can be relative or absolute.
+
+Alternatively, the options can be passed as a config file for convenience:
+
+<tt>testharness \-\-config testsprite2_sample.config</tt>
+
+For a sample, take a look at the *.config files in this repository.
+
+We can also pass a config file and override certain options as necessary:
+<tt>testharness \-\-config testsprite2_sample.config \-\-num-variations 10</tt>
+
+Note: You may find it convenient to copy the SUT executable along with any
+resources to the test harness directory. Also note that testsprite2 and its
+resources (icon.bmp) are automatically copied when using the Visual Studio
+solution.
+
+\subsection usageexamples_subsec Usage examples:
+
+Passing a custom arguments string:
+<tt>testharness \-\-sutapp testsprite2 \-\-sutargs "\-\-cyclecolor \-\-blend mod
+\-\-iterations 2" \-\-action-config xyz.actions</tt>
+
+Using the random variator:
+<tt>testharness \-\-sutapp testsprite2 \-\-variator random \-\-num-variations 5
+\-\-parameter-config xyz.parameters \-\-action-config xyz.actions</tt>
+
+\subsection config_subsec Config Files
+Config files are an alternate way to pass parameters to the test harness. We
+describe the paramters in a config file and pass that to the test harness using
+the \-\-config option. The config file consists of lines of the form "x=y" where
+x is an option and y is it's value. For boolean options, we simply give the name
+of the option to indicate that it is to be passed to the testharness.
+
+The hash '#' character can be used to start a comment from that point to the end
+of the line.
+
+\section paramconfig_sec The SUT Parameters File
+To generate variations we need to describe the parameters the will be passed to
+the SUT. This description is given in a parameters file. Each line of the parameters
+file (except the blank lines) represents one command line option with five
+comma separated fields:
+<tt>name, type, values, required, categories</tt>
+
+\li \c name is the name of the option, e.g., \c \-\-cyclecolor.
+\li \c type can have one of three values - integer, boolean and enum.
+\li \c values - for integer options this is the valid range of values the option
+	can take, i.e., [min max]. For enum options this is a list of strings that
+	the option can take, e.g., [val1 val2 val3]. For boolean options this field
+	is ignored.
+\li \c required - true if the option is required, false otherwise.
+\li \c categories - a list of categories that the option belongs to. For example,
+	[video mouse audio]
+
+Just like with config files, hash characters can be used to start comments.
+
+\subsection additionalnotes_subsec Additional Notes
+
+\li If you want to have an option that always takes a certain value, use an enum
+	with only one value.
+\li Currently there isn't any way to turn an option off, i.e., all options will
+	be included in the command line options string that is generated using the
+	config. If you don't want an option to be passed to the SUT, remove it from
+	the config file or comment it out.
+
+\section variators_sec Variators
+Variators are the mechanism by which we generate strings of command line arguments
+to test the SUT with. A variator is quite simply an iterator that iterates through
+different variations of command line options. There are two variators supported at
+the moment:
+\li \b Exhaustive - Generate all possible combinations of command line arguments
+	that are valid.
+\li \b Random - Generate a random variation each time the variator is called.
+
+As an example, let's try a simple .parameters file:\n
+<tt>
+\-\-blend, enum, [add mod], false, [] \n
+\-\-fullscreen, boolean, [], false, []
+</tt>
+
+The exhaustive variator would generate the following four variations:\n
+<tt>
+\-\-blend add \n
+\-\-blend mod \n
+\-\-blend add \-\-fullscreen \n
+\-\-blend mod \-\-fullscreen \n
+</tt>
+
+The random variator would simply generate a random variation like the following:\n
+<tt>\-\-blend mod</tt>
+
+\section actionconfig_sec The Actions File
+Once the SUT process has been launched, automated testing happens using a mechanism
+called actions. A list of actions is read from a file and each action is performed
+on the SUT process sequentially. Each line in the actions file describes an action.
+The format for an action is <tt>hh:mm:ss ACTION_NAME additional parameters</tt>.
+There are five actions supported at the moment:
+\li \b SCREENSHOT - Takes a screenshot of each window owned by the SUT process. The
+	images are saved as \c [hash]_[i].bmp where \c [hash] is the 32 character long
+	hexadecimal MD5 hash of the arguments string that was passed to the SUT while
+	launching it and \c i is the window number. i = 1 is an exceptional case
+	where the \c _[i] is dropped and the filename is simply \c [hash].bmp\n
+	Note: The screenshots are only of the window's client area.
+\li \b VERIFY - Verifies the screenshots taken by the last SCREENSHOT action by
+	comparing them against a verification image. Each \c [hash]_i.bmp image output
+	by the SCREENSHOT action is compared against a \c [hash].bmp image in the
+	verify-dir.
+\li \b QUIT - Gracefully quits the SUT process. On Windows this means sending a
+	WM_CLOSE message to each window owned by the SUT process. On Linux it means
+	sending a SIGQUIT signal to the SUT process.
+\li \b KILL - Forcefully kills the SUT process. This is useful when the SUT process
+	doesn't respond to the QUIT action.
+\li <b>LAUNCH [/path/to/executable] [args]</b> - Runs an executable with \c [args]
+	as the arguments string.
+
+Just like with config files, hash characters can be used to start comments.
+
+\section contint_sec Continuous Integration (CI)
+One of the goals of the project was to create a test harness that integrates
+with CI systems to provide automated visual and interactive testing to SDL.
+
+At the moment the test harness can be run in two modes that are useful for CI:
+\li Crash testing mode - launch the SUT with every variation and all parameters,
+	report to the CI if there's a crash
+\li Visual testing mode - launch and visually verify the SUT for a smaller subset
+	of the parameters
+
+Look at the launch_harness.sh/launch_harness.cmd for an example scripts that run the
+test harness for all variations with all parameters and report an error on a crash.
+The script uses the testsprite2_crashtest config, so remember to copy those files
+over to the test harness executable directory along with the script.
+
+\section todo_sec TODOs
+\li Allow specifying a clipping box along with the VERIFY action, i.e., hh:mm:ss
+	VERIFY x, y, w, h
+\li Add support for spaces between the equals sign in test harness config files
+\li Implement the SCREENSHOT action on Linux
+\li Add a pairwise variator
+\li Add actions to inject keyboard/mouse events
+\li Add actions to manipulate the SUT window, e.g., minimize, restore, resize
+\li Add support to load and save screenshots as .pngs instead of .bmps
+
+\section issues_sec Known Issues
+\li The QUIT action does not work on a testsprite2 process with multiple windows.
+	This appears to be an issue with testsprite2.
+\li The SCREENSHOT action doesn't capture the testsprite2 window correctly if the
+	--fullscreen option is supplied. It works with --fullscreen-desktop, however.
+
+\section moreinfo_sec More Information
+
+Author Contact Info:\n
+Apoorv Upreti \c \<apoorvupreti@gmail.com\>
+
+Other useful links:
+- Project Repository: https://bitbucket.org/nerdap/sdlvisualtest
+- Project Wiki: https://github.com/nerdap/autotestsprite2/wiki
+- Project Blog: http://nerdap.github.io
+- Verification images for testsprite2_blendmodes: https://www.dropbox.com/s/nm02aem76m812ng/testsprite2_blendmodes.zip
+- Verification images for testsprite2_geometry: https://www.dropbox.com/s/csypwryopaslpaf/testsprite2_geometry.zip
+*/

data/ext/alphatau/native/sdl/visualtest/acinclude.m4

@@ -0,0 +1,359 @@
+# Configure paths for SDL
+# Sam Lantinga 9/21/99
+# stolen from Manish Singh
+# stolen back from Frank Belew
+# stolen from Manish Singh
+# Shamelessly stolen from Owen Taylor
+
+# serial 1
+
+dnl AM_PATH_SDL([MINIMUM-VERSION, [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]]])
+dnl Test for SDL, and define SDL_CFLAGS and SDL_LIBS
+dnl
+AC_DEFUN([AM_PATH_SDL2],
+[dnl 
+dnl Get the cflags and libraries from the sdl2-config script
+dnl
+AC_ARG_WITH(sdl-prefix,[  --with-sdl-prefix=PFX   Prefix where SDL is installed (optional)],
+            sdl_prefix="$withval", sdl_prefix="")
+AC_ARG_WITH(sdl-exec-prefix,[  --with-sdl-exec-prefix=PFX Exec prefix where SDL is installed (optional)],
+            sdl_exec_prefix="$withval", sdl_exec_prefix="")
+AC_ARG_ENABLE(sdltest, [  --disable-sdltest       Do not try to compile and run a test SDL program],
+		    , enable_sdltest=yes)
+
+  min_sdl_version=ifelse([$1], ,0.9.0,$1)
+
+  if test "x$sdl_prefix$sdl_exec_prefix" = x ; then
+    PKG_CHECK_MODULES([SDL], [sdl2 >= $min_sdl_version],
+           [sdl_pc=yes],
+           [sdl_pc=no])
+  else
+    sdl_pc=no
+    if test x$sdl_exec_prefix != x ; then
+      sdl_config_args="$sdl_config_args --exec-prefix=$sdl_exec_prefix"
+      if test x${SDL_CONFIG+set} != xset ; then
+        SDL_CONFIG=$sdl_exec_prefix/bin/sdl2-config
+      fi
+    fi
+    if test x$sdl_prefix != x ; then
+      sdl_config_args="$sdl_config_args --prefix=$sdl_prefix"
+      if test x${SDL_CONFIG+set} != xset ; then
+        SDL_CONFIG=$sdl_prefix/bin/sdl2-config
+      fi
+    fi
+  fi
+
+  if test "x$sdl_pc" = xyes ; then
+    no_sdl=""
+    SDL_CONFIG="pkg-config sdl2"
+  else
+    as_save_PATH="$PATH"
+    if test "x$prefix" != xNONE && test "$cross_compiling" != yes; then
+      PATH="$prefix/bin:$prefix/usr/bin:$PATH"
+    fi
+    AC_PATH_PROG(SDL_CONFIG, sdl2-config, no, [$PATH])
+    PATH="$as_save_PATH"
+    AC_MSG_CHECKING(for SDL - version >= $min_sdl_version)
+    no_sdl=""
+
+    if test "$SDL_CONFIG" = "no" ; then
+      no_sdl=yes
+    else
+      SDL_CFLAGS=`$SDL_CONFIG $sdl_config_args --cflags`
+      SDL_LIBS=`$SDL_CONFIG $sdl_config_args --libs`
+
+      sdl_major_version=`$SDL_CONFIG $sdl_config_args --version | \
+             sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'`
+      sdl_minor_version=`$SDL_CONFIG $sdl_config_args --version | \
+             sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'`
+      sdl_micro_version=`$SDL_CONFIG $sdl_config_args --version | \
+             sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'`
+      if test "x$enable_sdltest" = "xyes" ; then
+        ac_save_CFLAGS="$CFLAGS"
+        ac_save_CXXFLAGS="$CXXFLAGS"
+        ac_save_LIBS="$LIBS"
+        CFLAGS="$CFLAGS $SDL_CFLAGS"
+        CXXFLAGS="$CXXFLAGS $SDL_CFLAGS"
+        LIBS="$LIBS $SDL_LIBS"
+dnl
+dnl Now check if the installed SDL is sufficiently new. (Also sanity
+dnl checks the results of sdl2-config to some extent
+dnl
+      rm -f conf.sdltest
+      AC_TRY_RUN([
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include "SDL.h"
+
+char*
+my_strdup (char *str)
+{
+  char *new_str;
+  
+  if (str)
+    {
+      new_str = (char *)malloc ((strlen (str) + 1) * sizeof(char));
+      strcpy (new_str, str);
+    }
+  else
+    new_str = NULL;
+  
+  return new_str;
+}
+
+int main (int argc, char *argv[])
+{
+  int major, minor, micro;
+  char *tmp_version;
+
+  /* This hangs on some systems (?)
+  system ("touch conf.sdltest");
+  */
+  { FILE *fp = fopen("conf.sdltest", "a"); if ( fp ) fclose(fp); }
+
+  /* HP/UX 9 (%@#!) writes to sscanf strings */
+  tmp_version = my_strdup("$min_sdl_version");
+  if (sscanf(tmp_version, "%d.%d.%d", &major, &minor, &micro) != 3) {
+     printf("%s, bad version string\n", "$min_sdl_version");
+     exit(1);
+   }
+
+   if (($sdl_major_version > major) ||
+      (($sdl_major_version == major) && ($sdl_minor_version > minor)) ||
+      (($sdl_major_version == major) && ($sdl_minor_version == minor) && ($sdl_micro_version >= micro)))
+    {
+      return 0;
+    }
+  else
+    {
+      printf("\n*** 'sdl2-config --version' returned %d.%d.%d, but the minimum version\n", $sdl_major_version, $sdl_minor_version, $sdl_micro_version);
+      printf("*** of SDL required is %d.%d.%d. If sdl2-config is correct, then it is\n", major, minor, micro);
+      printf("*** best to upgrade to the required version.\n");
+      printf("*** If sdl2-config was wrong, set the environment variable SDL_CONFIG\n");
+      printf("*** to point to the correct copy of sdl2-config, and remove the file\n");
+      printf("*** config.cache before re-running configure\n");
+      return 1;
+    }
+}
+
+],, no_sdl=yes,[echo $ac_n "cross compiling; assumed OK... $ac_c"])
+        CFLAGS="$ac_save_CFLAGS"
+        CXXFLAGS="$ac_save_CXXFLAGS"
+        LIBS="$ac_save_LIBS"
+      fi
+    fi
+    if test "x$no_sdl" = x ; then
+      AC_MSG_RESULT(yes)
+    else
+      AC_MSG_RESULT(no)
+    fi
+  fi
+  if test "x$no_sdl" = x ; then
+     ifelse([$2], , :, [$2])
+  else
+     if test "$SDL_CONFIG" = "no" ; then
+       echo "*** The sdl2-config script installed by SDL could not be found"
+       echo "*** If SDL was installed in PREFIX, make sure PREFIX/bin is in"
+       echo "*** your path, or set the SDL_CONFIG environment variable to the"
+       echo "*** full path to sdl2-config."
+     else
+       if test -f conf.sdltest ; then
+        :
+       else
+          echo "*** Could not run SDL test program, checking why..."
+          CFLAGS="$CFLAGS $SDL_CFLAGS"
+          CXXFLAGS="$CXXFLAGS $SDL_CFLAGS"
+          LIBS="$LIBS $SDL_LIBS"
+          AC_TRY_LINK([
+#include <stdio.h>
+#include "SDL.h"
+
+int main(int argc, char *argv[])
+{ return 0; }
+#undef  main
+#define main K_and_R_C_main
+],      [ return 0; ],
+        [ echo "*** The test program compiled, but did not run. This usually means"
+          echo "*** that the run-time linker is not finding SDL or finding the wrong"
+          echo "*** version of SDL. If it is not finding SDL, you'll need to set your"
+          echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point"
+          echo "*** to the installed location  Also, make sure you have run ldconfig if that"
+          echo "*** is required on your system"
+	  echo "***"
+          echo "*** If you have an old version installed, it is best to remove it, although"
+          echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH"],
+        [ echo "*** The test program failed to compile or link. See the file config.log for the"
+          echo "*** exact error that occured. This usually means SDL was incorrectly installed"
+          echo "*** or that you have moved SDL since it was installed. In the latter case, you"
+          echo "*** may want to edit the sdl2-config script: $SDL_CONFIG" ])
+          CFLAGS="$ac_save_CFLAGS"
+          CXXFLAGS="$ac_save_CXXFLAGS"
+          LIBS="$ac_save_LIBS"
+       fi
+     fi
+     SDL_CFLAGS=""
+     SDL_LIBS=""
+     ifelse([$3], , :, [$3])
+  fi
+  AC_SUBST(SDL_CFLAGS)
+  AC_SUBST(SDL_LIBS)
+  rm -f conf.sdltest
+])
+# pkg.m4 - Macros to locate and utilise pkg-config.            -*- Autoconf -*-
+# serial 1 (pkg-config-0.24)
+# 
+# Copyright © 2004 Scott James Remnant <scott@netsplit.com>.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+#
+# As a special exception to the GNU General Public License, if you
+# distribute this file as part of a program that contains a
+# configuration script generated by Autoconf, you may include it under
+# the same distribution terms that you use for the rest of that program.
+
+# PKG_PROG_PKG_CONFIG([MIN-VERSION])
+# ----------------------------------
+AC_DEFUN([PKG_PROG_PKG_CONFIG],
+[m4_pattern_forbid([^_?PKG_[A-Z_]+$])
+m4_pattern_allow([^PKG_CONFIG(_PATH)?$])
+AC_ARG_VAR([PKG_CONFIG], [path to pkg-config utility])
+AC_ARG_VAR([PKG_CONFIG_PATH], [directories to add to pkg-config's search path])
+AC_ARG_VAR([PKG_CONFIG_LIBDIR], [path overriding pkg-config's built-in search path])
+
+if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then
+	AC_PATH_TOOL([PKG_CONFIG], [pkg-config])
+fi
+if test -n "$PKG_CONFIG"; then
+	_pkg_min_version=m4_default([$1], [0.9.0])
+	AC_MSG_CHECKING([pkg-config is at least version $_pkg_min_version])
+	if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then
+		AC_MSG_RESULT([yes])
+	else
+		AC_MSG_RESULT([no])
+		PKG_CONFIG=""
+	fi
+fi[]dnl
+])# PKG_PROG_PKG_CONFIG
+
+# PKG_CHECK_EXISTS(MODULES, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
+#
+# Check to see whether a particular set of modules exists.  Similar
+# to PKG_CHECK_MODULES(), but does not set variables or print errors.
+#
+# Please remember that m4 expands AC_REQUIRE([PKG_PROG_PKG_CONFIG])
+# only at the first occurence in configure.ac, so if the first place
+# it's called might be skipped (such as if it is within an "if", you
+# have to call PKG_CHECK_EXISTS manually
+# --------------------------------------------------------------
+AC_DEFUN([PKG_CHECK_EXISTS],
+[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl
+if test -n "$PKG_CONFIG" && \
+    AC_RUN_LOG([$PKG_CONFIG --exists --print-errors "$1"]); then
+  m4_default([$2], [:])
+m4_ifvaln([$3], [else
+  $3])dnl
+fi])
+
+# _PKG_CONFIG([VARIABLE], [COMMAND], [MODULES])
+# ---------------------------------------------
+m4_define([_PKG_CONFIG],
+[if test -n "$$1"; then
+    pkg_cv_[]$1="$$1"
+ elif test -n "$PKG_CONFIG"; then
+    PKG_CHECK_EXISTS([$3],
+                     [pkg_cv_[]$1=`$PKG_CONFIG --[]$2 "$3" 2>/dev/null`],
+		     [pkg_failed=yes])
+ else
+    pkg_failed=untried
+fi[]dnl
+])# _PKG_CONFIG
+
+# _PKG_SHORT_ERRORS_SUPPORTED
+# -----------------------------
+AC_DEFUN([_PKG_SHORT_ERRORS_SUPPORTED],
+[AC_REQUIRE([PKG_PROG_PKG_CONFIG])
+if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then
+        _pkg_short_errors_supported=yes
+else
+        _pkg_short_errors_supported=no
+fi[]dnl
+])# _PKG_SHORT_ERRORS_SUPPORTED
+
+
+# PKG_CHECK_MODULES(VARIABLE-PREFIX, MODULES, [ACTION-IF-FOUND],
+# [ACTION-IF-NOT-FOUND])
+#
+#
+# Note that if there is a possibility the first call to
+# PKG_CHECK_MODULES might not happen, you should be sure to include an
+# explicit call to PKG_PROG_PKG_CONFIG in your configure.ac
+#
+#
+# --------------------------------------------------------------
+AC_DEFUN([PKG_CHECK_MODULES],
+[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl
+AC_ARG_VAR([$1][_CFLAGS], [C compiler flags for $1, overriding pkg-config])dnl
+AC_ARG_VAR([$1][_LIBS], [linker flags for $1, overriding pkg-config])dnl
+
+pkg_failed=no
+AC_MSG_CHECKING([for $1])
+
+_PKG_CONFIG([$1][_CFLAGS], [cflags], [$2])
+_PKG_CONFIG([$1][_LIBS], [libs], [$2])
+
+m4_define([_PKG_TEXT], [Alternatively, you may set the environment variables $1[]_CFLAGS
+and $1[]_LIBS to avoid the need to call pkg-config.
+See the pkg-config man page for more details.])
+
+if test $pkg_failed = yes; then
+   	AC_MSG_RESULT([no])
+        _PKG_SHORT_ERRORS_SUPPORTED
+        if test $_pkg_short_errors_supported = yes; then
+	        $1[]_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors "$2" 2>&1`
+        else 
+	        $1[]_PKG_ERRORS=`$PKG_CONFIG --print-errors "$2" 2>&1`
+        fi
+	# Put the nasty error message in config.log where it belongs
+	echo "$$1[]_PKG_ERRORS" >&AS_MESSAGE_LOG_FD
+
+	m4_default([$4], [AC_MSG_ERROR(
+[Package requirements ($2) were not met:
+
+$$1_PKG_ERRORS
+
+Consider adjusting the PKG_CONFIG_PATH environment variable if you
+installed software in a non-standard prefix.
+
+_PKG_TEXT])dnl
+        ])
+elif test $pkg_failed = untried; then
+     	AC_MSG_RESULT([no])
+	m4_default([$4], [AC_MSG_FAILURE(
+[The pkg-config script could not be found or is too old.  Make sure it
+is in your PATH or set the PKG_CONFIG environment variable to the full
+path to pkg-config.
+
+_PKG_TEXT
+
+To get pkg-config, see <http://pkg-config.freedesktop.org/>.])dnl
+        ])
+else
+	$1[]_CFLAGS=$pkg_cv_[]$1[]_CFLAGS
+	$1[]_LIBS=$pkg_cv_[]$1[]_LIBS
+        AC_MSG_RESULT([yes])
+	$3
+fi[]dnl
+])# PKG_CHECK_MODULES