comparison: configure.ac
configure.ac
- changeset 11146
- c56333373e3c
- parent 11098
- bd0d55db0d73
- child 11147
- 67309baf4c84
equal
deleted
inserted
replaced
| 11145:5320b2d70270 | 11146:c56333373e3c |
|---|---|
| 308 dnl # Check for DBUS libraries | 308 dnl # Check for DBUS libraries |
| 309 dnl ####################################################################### | 309 dnl ####################################################################### |
| 310 | 310 |
| 311 AC_ARG_ENABLE(dbus, [ --enable-dbus enable DBUS support],,enable_dbus=no) | 311 AC_ARG_ENABLE(dbus, [ --enable-dbus enable DBUS support],,enable_dbus=no) |
| 312 | 312 |
| 313 if test "x$enable_dbus" = "xyes"; then | 313 if test "x$enable_dbus" = "xyes" ; then |
| 314 AC_CHECK_PROG(enable_dbus, dbus-binding-tool, yes, no) | 314 AC_CHECK_PROG(enable_dbus, dbus-binding-tool, yes, no) |
| 315 fi | 315 fi |
| 316 | 316 |
| 317 if test "x$enable_dbus" = "xyes"; then | 317 if test "x$enable_dbus" = "xyes" ; then |
| 318 PKG_CHECK_MODULES(DBUS, [dbus-1 >= 0.34 dbus-glib-1 >= 0.34], | 318 PKG_CHECK_MODULES(DBUS, [dbus-1 >= 0.35 dbus-glib-1 >= 0.35], |
| 319 [ | 319 [ |
| 320 AC_SUBST(DBUS_CFLAGS) | 320 AC_SUBST(DBUS_CFLAGS) |
| 321 AC_SUBST(DBUS_LIBS) | 321 AC_SUBST(DBUS_LIBS) |
| 322 enable_dbus=yes | 322 enable_dbus=yes |
| 323 ], | 323 ], |
| 329 AC_MSG_WARN([dbus-binding-tool executable not found in your path]) | 329 AC_MSG_WARN([dbus-binding-tool executable not found in your path]) |
| 330 enable_dbus=no | 330 enable_dbus=no |
| 331 fi | 331 fi |
| 332 fi | 332 fi |
| 333 | 333 |
| 334 if test "x$enable_dbus" = "xyes"; then | 334 dnl Why do we need python? |
| 335 | |
| 336 dnl Python scripts are used to auto-generate about 3000 lines of C | |
| 337 dnl and XML code that wraps (part of) the existing Gaim API so that | |
| 338 dnl it is now accessible through DBUS. | |
| 339 | |
| 340 dnl Python is only required if --enable-dbus is used, and only for | |
| 341 dnl the build process to generate the code, not for running gaim. | |
| 342 dnl This autogenerated code is system-independent, so in principle we | |
| 343 dnl can generate all of it before shipping. But I thought adding | |
| 344 dnl auto-generated stuff to the CVS is inelegant. Alternatively, | |
| 345 dnl these python scripts could be rewritten in C (brrrr ...). | |
| 346 | |
| 347 if test "x$enable_dbus" = "xyes" ; then | |
| 348 AC_PATH_PROG([PYTHON], [python], [no]) | |
| 349 if test "x$PYTHON" = "xno" ; then | |
| 350 AC_MSG_WARN([python interpreter not found in your path]) | |
| 351 enable_dbus=no | |
| 352 fi | |
| 353 fi | |
| 354 | |
| 355 if test "x$enable_dbus" = "xyes" ; then | |
| 356 if $PYTHON -c "import sys; sys.exit(sys.version[[:3]] >= '2.4')" ; then | |
| 357 AC_MSG_WARN([python version >= 2.4 required]) | |
| 358 enable_dbus=no | |
| 359 fi | |
| 360 fi | |
| 361 | |
| 362 if test "x$enable_dbus" = "xyes" ; then | |
| 335 AC_DEFINE(HAVE_DBUS, 1, [Define if we're using DBUS.]) | 363 AC_DEFINE(HAVE_DBUS, 1, [Define if we're using DBUS.]) |
| 336 echo "Building with DBUS support" | 364 echo "Building with DBUS support" |
| 337 else | 365 else |
| 338 echo "Building without DBUS support" | 366 echo "Building without DBUS support" |
| 339 fi | 367 fi |
