2013-11-10 17:55:40 +01:00
|
|
|
AC_PREREQ([2.64])
|
|
|
|
|
|
|
|
|
|
m4_define([libinput_major_version], [0])
|
2014-12-05 12:08:22 +10:00
|
|
|
m4_define([libinput_minor_version], [7])
|
2014-02-26 19:54:51 +01:00
|
|
|
m4_define([libinput_micro_version], [0])
|
2013-11-10 17:55:40 +01:00
|
|
|
m4_define([libinput_version],
|
|
|
|
|
[libinput_major_version.libinput_minor_version.libinput_micro_version])
|
|
|
|
|
|
|
|
|
|
AC_INIT([libinput],
|
|
|
|
|
[libinput_version],
|
2014-02-26 19:54:27 +01:00
|
|
|
[https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=libinput&version=libinput_version],
|
2013-11-10 17:55:40 +01:00
|
|
|
[libinput],
|
2014-02-26 19:54:27 +01:00
|
|
|
[http://www.freedesktop.org/wiki/Software/libinput/])
|
2013-11-10 17:55:40 +01:00
|
|
|
|
|
|
|
|
AC_SUBST([LIBINPUT_VERSION_MAJOR], [libinput_major_version])
|
|
|
|
|
AC_SUBST([LIBINPUT_VERSION_MINOR], [libinput_minor_version])
|
|
|
|
|
AC_SUBST([LIBINPUT_VERSION_MICRO], [libinput_micro_version])
|
|
|
|
|
AC_SUBST([LIBINPUT_VERSION], [libinput_version])
|
|
|
|
|
|
|
|
|
|
AC_CONFIG_HEADERS([config.h])
|
|
|
|
|
AC_CONFIG_MACRO_DIR([m4])
|
|
|
|
|
|
2014-12-05 12:52:22 +10:00
|
|
|
AM_INIT_AUTOMAKE([1.11 foreign no-dist-gzip dist-xz])
|
2013-11-10 17:55:40 +01:00
|
|
|
|
2014-05-22 08:06:25 +02:00
|
|
|
# Before making a release, the LIBINPUT_LT_VERSION string should be
|
|
|
|
|
# modified.
|
|
|
|
|
# The string is of the form C:R:A.
|
|
|
|
|
# - If interfaces have been changed or added, but binary compatibility has
|
|
|
|
|
# been preserved, change to C+1:0:A+1
|
|
|
|
|
# - If binary compatibility has been broken (eg removed or changed interfaces)
|
|
|
|
|
# change to C+1:0:0
|
|
|
|
|
# - If the interface is the same as the previous version, change to C:R+1:A
|
2014-12-05 12:08:22 +10:00
|
|
|
LIBINPUT_LT_VERSION=6:0:1
|
2014-05-22 08:06:25 +02:00
|
|
|
AC_SUBST(LIBINPUT_LT_VERSION)
|
|
|
|
|
|
2013-11-10 17:55:40 +01:00
|
|
|
AM_SILENT_RULES([yes])
|
|
|
|
|
|
|
|
|
|
# Check for programs
|
2013-12-06 14:52:38 +10:00
|
|
|
AC_PROG_CC_C99
|
2014-03-29 14:39:42 +01:00
|
|
|
AC_PROG_CXX # Only used by build C++ test
|
2013-11-10 17:55:40 +01:00
|
|
|
|
|
|
|
|
# Initialize libtool
|
|
|
|
|
LT_PREREQ([2.2])
|
|
|
|
|
LT_INIT
|
|
|
|
|
|
2013-11-17 11:19:50 +01:00
|
|
|
AC_CHECK_DECL(EPOLL_CLOEXEC, [],
|
|
|
|
|
[AC_MSG_ERROR("EPOLL_CLOEXEC is needed to compile libinput")],
|
|
|
|
|
[[#include <sys/epoll.h>]])
|
2013-11-10 17:55:40 +01:00
|
|
|
AC_CHECK_DECL(TFD_CLOEXEC,[],
|
|
|
|
|
[AC_MSG_ERROR("TFD_CLOEXEC is needed to compile libinput")],
|
|
|
|
|
[[#include <sys/timerfd.h>]])
|
|
|
|
|
AC_CHECK_DECL(CLOCK_MONOTONIC,[],
|
|
|
|
|
[AC_MSG_ERROR("CLOCK_MONOTONIC is needed to compile libinput")],
|
|
|
|
|
[[#include <time.h>]])
|
|
|
|
|
|
|
|
|
|
PKG_PROG_PKG_CONFIG()
|
|
|
|
|
PKG_CHECK_MODULES(MTDEV, [mtdev >= 1.1.0])
|
2013-12-09 16:21:06 +10:00
|
|
|
PKG_CHECK_MODULES(LIBUDEV, [libudev])
|
2013-12-06 12:01:47 +10:00
|
|
|
PKG_CHECK_MODULES(LIBEVDEV, [libevdev >= 0.4])
|
2014-07-03 09:29:22 +10:00
|
|
|
AC_CHECK_LIB([m], [atan2])
|
2014-07-03 09:30:40 +10:00
|
|
|
AC_CHECK_LIB([rt], [clock_gettime])
|
2013-11-10 17:55:40 +01:00
|
|
|
|
|
|
|
|
if test "x$GCC" = "xyes"; then
|
2014-06-06 09:38:35 +10:00
|
|
|
GCC_CXXFLAGS="-Wall -Wextra -Wno-unused-parameter -g -fvisibility=hidden"
|
|
|
|
|
GCC_CFLAGS="$GCC_CXXFLAGS -Wmissing-prototypes -Wstrict-prototypes"
|
2013-11-10 17:55:40 +01:00
|
|
|
fi
|
|
|
|
|
AC_SUBST(GCC_CFLAGS)
|
2014-06-06 09:38:35 +10:00
|
|
|
AC_SUBST(GCC_CXXFLAGS)
|
2013-11-10 17:55:40 +01:00
|
|
|
|
2013-12-06 09:58:00 +10:00
|
|
|
AC_PATH_PROG(DOXYGEN, [doxygen])
|
|
|
|
|
if test "x$DOXYGEN" = "x"; then
|
|
|
|
|
AC_MSG_WARN([doxygen not found - required for documentation])
|
|
|
|
|
have_doxygen="no"
|
|
|
|
|
else
|
|
|
|
|
have_doxygen="yes"
|
|
|
|
|
fi
|
|
|
|
|
AM_CONDITIONAL([HAVE_DOXYGEN], [test "x$have_doxygen" = "xyes"])
|
|
|
|
|
|
2014-05-27 15:29:55 +10:00
|
|
|
AC_ARG_ENABLE(event-gui,
|
|
|
|
|
AS_HELP_STRING([--enable-event-gui], [Build the GUI event viewer (default=auto)]),
|
|
|
|
|
[build_eventgui="$enableval"],
|
|
|
|
|
[build_eventgui="auto"])
|
|
|
|
|
PKG_CHECK_EXISTS([cairo glib-2.0 gtk+-3.0], [HAVE_GUILIBS="yes"], [HAVE_GUILIBS="no"])
|
|
|
|
|
|
|
|
|
|
if test "x$build_eventgui" = "xauto"; then
|
|
|
|
|
build_eventgui="$HAVE_GUILIBS"
|
|
|
|
|
fi
|
|
|
|
|
if test "x$build_eventgui" = "xyes"; then
|
|
|
|
|
PKG_CHECK_MODULES(CAIRO, [cairo])
|
|
|
|
|
PKG_CHECK_MODULES(GTK, [glib-2.0 gtk+-3.0])
|
|
|
|
|
fi
|
|
|
|
|
AM_CONDITIONAL(BUILD_EVENTGUI, [test "x$build_eventgui" = "xyes"])
|
|
|
|
|
|
2013-12-06 14:17:35 +10:00
|
|
|
AC_ARG_ENABLE(tests,
|
Add a device test suite
A rather large commit, copied from a similar (almost identical) suite in
libtouchpad and ported for libinput.
The goal here is to make testing for various devices easy, so the litest
("libinput test") wrappers do that. The idea is that each device has some
features, and tests are likely to exercise some features or won't work with
other features.
Each test case takes a list of required features and a list of excluded
features. The test suite will create a new test case for each device in the
suite that matches that set.
For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would
run on clickpads only, not on touchpads with buttons.
check supports suites and test cases, both named. We wrap that so that each
named set of cases we add are a test suite, with the set of devices being the
test cases. i.e.
litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY);
adds a suite named "foo:bar" and test cases for both devices given, with their
shortnames as test case name, resulting in:
"foo:bar", "trackpoint"
"foo:bar", "clickpad"
...
Multiple test functions can be added to a suite. For tests without a device
requirement there is litest_add_no_device_test(...).
The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow
the set of test cases. The test suite detects when run inside a debugger and
disables fork mode (the default).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
|
|
|
AS_HELP_STRING([--enable-tests], [Build the tests (default=auto)]),
|
2013-12-06 14:17:35 +10:00
|
|
|
[build_tests="$enableval"],
|
Add a device test suite
A rather large commit, copied from a similar (almost identical) suite in
libtouchpad and ported for libinput.
The goal here is to make testing for various devices easy, so the litest
("libinput test") wrappers do that. The idea is that each device has some
features, and tests are likely to exercise some features or won't work with
other features.
Each test case takes a list of required features and a list of excluded
features. The test suite will create a new test case for each device in the
suite that matches that set.
For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would
run on clickpads only, not on touchpads with buttons.
check supports suites and test cases, both named. We wrap that so that each
named set of cases we add are a test suite, with the set of devices being the
test cases. i.e.
litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY);
adds a suite named "foo:bar" and test cases for both devices given, with their
shortnames as test case name, resulting in:
"foo:bar", "trackpoint"
"foo:bar", "clickpad"
...
Multiple test functions can be added to a suite. For tests without a device
requirement there is litest_add_no_device_test(...).
The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow
the set of test cases. The test suite detects when run inside a debugger and
disables fork mode (the default).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
|
|
|
[build_tests="auto"])
|
|
|
|
|
|
2014-09-10 01:32:24 +02:00
|
|
|
PKG_CHECK_MODULES(CHECK, [check >= 0.9.10], [HAVE_CHECK="yes"], [HAVE_CHECK="no"])
|
Add a device test suite
A rather large commit, copied from a similar (almost identical) suite in
libtouchpad and ported for libinput.
The goal here is to make testing for various devices easy, so the litest
("libinput test") wrappers do that. The idea is that each device has some
features, and tests are likely to exercise some features or won't work with
other features.
Each test case takes a list of required features and a list of excluded
features. The test suite will create a new test case for each device in the
suite that matches that set.
For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would
run on clickpads only, not on touchpads with buttons.
check supports suites and test cases, both named. We wrap that so that each
named set of cases we add are a test suite, with the set of devices being the
test cases. i.e.
litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY);
adds a suite named "foo:bar" and test cases for both devices given, with their
shortnames as test case name, resulting in:
"foo:bar", "trackpoint"
"foo:bar", "clickpad"
...
Multiple test functions can be added to a suite. For tests without a device
requirement there is litest_add_no_device_test(...).
The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow
the set of test cases. The test suite detects when run inside a debugger and
disables fork mode (the default).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
|
|
|
|
|
|
|
|
if test "x$build_tests" = "xauto"; then
|
2014-05-27 13:47:58 +10:00
|
|
|
build_tests="$HAVE_CHECK"
|
Add a device test suite
A rather large commit, copied from a similar (almost identical) suite in
libtouchpad and ported for libinput.
The goal here is to make testing for various devices easy, so the litest
("libinput test") wrappers do that. The idea is that each device has some
features, and tests are likely to exercise some features or won't work with
other features.
Each test case takes a list of required features and a list of excluded
features. The test suite will create a new test case for each device in the
suite that matches that set.
For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would
run on clickpads only, not on touchpads with buttons.
check supports suites and test cases, both named. We wrap that so that each
named set of cases we add are a test suite, with the set of devices being the
test cases. i.e.
litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY);
adds a suite named "foo:bar" and test cases for both devices given, with their
shortnames as test case name, resulting in:
"foo:bar", "trackpoint"
"foo:bar", "clickpad"
...
Multiple test functions can be added to a suite. For tests without a device
requirement there is litest_add_no_device_test(...).
The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow
the set of test cases. The test suite detects when run inside a debugger and
disables fork mode (the default).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
|
|
|
fi
|
2014-03-27 11:04:24 +10:00
|
|
|
if test "x$build_tests" = "xyes"; then
|
|
|
|
|
if test "x$HAVE_CHECK" = "xno"; then
|
|
|
|
|
AC_MSG_ERROR([Cannot build tests, check is missing])
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
AC_PATH_PROG(VALGRIND, [valgrind])
|
Add a device test suite
A rather large commit, copied from a similar (almost identical) suite in
libtouchpad and ported for libinput.
The goal here is to make testing for various devices easy, so the litest
("libinput test") wrappers do that. The idea is that each device has some
features, and tests are likely to exercise some features or won't work with
other features.
Each test case takes a list of required features and a list of excluded
features. The test suite will create a new test case for each device in the
suite that matches that set.
For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would
run on clickpads only, not on touchpads with buttons.
check supports suites and test cases, both named. We wrap that so that each
named set of cases we add are a test suite, with the set of devices being the
test cases. i.e.
litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY);
adds a suite named "foo:bar" and test cases for both devices given, with their
shortnames as test case name, resulting in:
"foo:bar", "trackpoint"
"foo:bar", "clickpad"
...
Multiple test functions can be added to a suite. For tests without a device
requirement there is litest_add_no_device_test(...).
The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow
the set of test cases. The test suite detects when run inside a debugger and
disables fork mode (the default).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
|
|
|
fi
|
2013-12-06 14:17:35 +10:00
|
|
|
|
2014-03-27 11:04:24 +10:00
|
|
|
AM_CONDITIONAL(HAVE_VALGRIND, [test "x$VALGRIND" != "x"])
|
2013-12-06 14:17:35 +10:00
|
|
|
AM_CONDITIONAL(BUILD_TESTS, [test "x$build_tests" = "xyes"])
|
|
|
|
|
|
2013-11-10 17:55:40 +01:00
|
|
|
AC_CONFIG_FILES([Makefile
|
2013-12-06 09:58:00 +10:00
|
|
|
doc/Makefile
|
|
|
|
|
doc/libinput.doxygen
|
2013-11-10 17:55:40 +01:00
|
|
|
src/Makefile
|
|
|
|
|
src/libinput.pc
|
2013-12-06 14:17:35 +10:00
|
|
|
src/libinput-version.h
|
2014-01-28 11:25:40 +10:00
|
|
|
test/Makefile
|
|
|
|
|
tools/Makefile])
|
2013-11-10 17:55:40 +01:00
|
|
|
AC_OUTPUT
|
2014-07-03 10:52:40 +10:00
|
|
|
|
|
|
|
|
AC_MSG_RESULT([
|
|
|
|
|
Prefix ${prefix}
|
|
|
|
|
|
|
|
|
|
Build documentation ${have_doxygen}
|
|
|
|
|
Build tests ${build_tests}
|
|
|
|
|
Tests use valgrind ${VALGRIND}
|
|
|
|
|
Build GUI event tool ${build_eventgui}
|
|
|
|
|
])
|
