ef5cb32a0f
The situation is this: even when we --disable-gtk-doc, if gtk-doc is actually installed at configure stage, tools like gtkdoc-rebase will be picked up and run during the install target. That is bad because the gtk-doc package may have been removed by then, especially during dpb(1) bulks (we explicitely disable support for it so why should it stay...). So for now, let's add the following env to configure whenever we use --disable-gtk-doc, until a bettersolution is found... CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \ ac_cv_path_GTKDOC_REBASE="" \ ac_cv_path_GTKDOC_MKPDF=""
41 lines
1.1 KiB
Makefile
41 lines
1.1 KiB
Makefile
# $OpenBSD: Makefile,v 1.36 2012/09/21 14:48:06 ajacoutot Exp $
|
|
|
|
COMMENT= abstraction layer between apps and connection managers
|
|
|
|
DISTNAME= telepathy-mission-control-5.12.0
|
|
REVISION= 0
|
|
|
|
SHARED_LIBS += mission-control-plugins 1.1 # 3.1
|
|
|
|
HOMEPAGE= http://mission-control.sourceforge.net/
|
|
|
|
MASTER_SITES= ${MASTER_SITES_TP:=telepathy-mission-control/}
|
|
|
|
WANTLIB += c dbus-1 dbus-glib-1 gio-2.0 glib-2.0 gmodule-2.0
|
|
WANTLIB += gobject-2.0 gthread-2.0 pcre pthread z telepathy-glib ffi
|
|
|
|
MODULES= devel/gettext \
|
|
lang/python
|
|
MODPY_RUNDEP= No
|
|
|
|
BUILD_DEPENDS= textproc/libxslt
|
|
LIB_DEPENDS= net/telepathy/telepathy-glib>=0.18.0
|
|
|
|
LIBTOOL_FLAGS= --tag=disable-static
|
|
|
|
CONFIGURE_ARGS+= ${CONFIGURE_SHARED} \
|
|
--disable-static \
|
|
--disable-gtk-doc \
|
|
--disable-gnome-keyring \
|
|
--disable-upower \
|
|
--enable-mcclient-so6 \
|
|
--with-connectivity=no
|
|
|
|
# If one of these tools is found at configure stage, it might be used,
|
|
# no matter whether we use --disable-gtk-doc or not.
|
|
CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \
|
|
ac_cv_path_GTKDOC_REBASE="" \
|
|
ac_cv_path_GTKDOC_MKPDF=""
|
|
|
|
.include <bsd.port.mk>
|