kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/sysutils/dbus-glib/buildlink3.mk

25 lines
788 B
Makefile
Raw Normal View History

Update to 0.71: D-Bus GLib Bindings 0.71 (24 July 2006) == - Correctly installs a few missing headers - Build was cleaned up a bit D-Bus GLib Bindings 0.70 (17 July 2006) == - First release after bindings split - dbus-binding-tool heeds org.freedesktop.DBus.GLib.ClientCSymbol C symbol name annotations when generating glib client bindings - DBusGProxy can now be inherited from - Support added for generating bindings to arrays that are represented as GPtrArrays rather than GArrays (ie size-variable things, such as strings, objects, structs, etc). - Modification of the existing specialised types to have N type parameters (rather than the current 1 or 2 for arrays and dictionaries respectively). You can then use this to get a glib type to represent any arbitrary D-Bus struct type using dbus_g_type_get_struct. The only implementation of these types is with GValueArrays as before, but it's now possible to store these in arrays, emit them in signals, etc. - New methodbus_g_connection_open provides a way to open connections to an arbitrary address - Various bugs and memory leaks fixed
2006-08-23 11:45:16 +02:00
# $NetBSD: buildlink3.mk,v 1.11 2006/08/23 09:45:16 jmmv Exp $
Initial import of dbus-glib, version 0.22: D-BUS is a message bus, used for sending messages between applications. Conceptually, it fits somewhere in between raw sockets and CORBA in terms of complexity. D-BUS supports broadcast messages, asynchronous messages (thus decreasing latency), authentication, and more. It is designed to be low-overhead; messages are sent using a binary protocol, not using XML. D-BUS also supports a method call mapping for its messages, but it is not required; this makes using the system quite simple. This package provides the D-BUS interface to GLib and the dbus-monitor utility (included here because it also uses GLib).
2004-10-11 19:46:41 +02:00
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+
DBUS_GLIB_BUILDLINK3_MK:= ${DBUS_GLIB_BUILDLINK3_MK}+
.if !empty(BUILDLINK_DEPTH:M+)
BUILDLINK_DEPENDS+= dbus-glib
.endif
BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Ndbus-glib}
BUILDLINK_PACKAGES+= dbus-glib
Change the format of BUILDLINK_ORDER to contain depth information as well, and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-09 01:10:35 +02:00
BUILDLINK_ORDER:= ${BUILDLINK_ORDER} ${BUILDLINK_DEPTH}dbus-glib
Initial import of dbus-glib, version 0.22: D-BUS is a message bus, used for sending messages between applications. Conceptually, it fits somewhere in between raw sockets and CORBA in terms of complexity. D-BUS supports broadcast messages, asynchronous messages (thus decreasing latency), authentication, and more. It is designed to be low-overhead; messages are sent using a binary protocol, not using XML. D-BUS also supports a method call mapping for its messages, but it is not required; this makes using the system quite simple. This package provides the D-BUS interface to GLib and the dbus-monitor utility (included here because it also uses GLib).
2004-10-11 19:46:41 +02:00
.if !empty(DBUS_GLIB_BUILDLINK3_MK:M+)
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
BUILDLINK_API_DEPENDS.dbus-glib+= dbus-glib>=0.61
Update to 0.71: D-Bus GLib Bindings 0.71 (24 July 2006) == - Correctly installs a few missing headers - Build was cleaned up a bit D-Bus GLib Bindings 0.70 (17 July 2006) == - First release after bindings split - dbus-binding-tool heeds org.freedesktop.DBus.GLib.ClientCSymbol C symbol name annotations when generating glib client bindings - DBusGProxy can now be inherited from - Support added for generating bindings to arrays that are represented as GPtrArrays rather than GArrays (ie size-variable things, such as strings, objects, structs, etc). - Modification of the existing specialised types to have N type parameters (rather than the current 1 or 2 for arrays and dictionaries respectively). You can then use this to get a glib type to represent any arbitrary D-Bus struct type using dbus_g_type_get_struct. The only implementation of these types is with GValueArrays as before, but it's now possible to store these in arrays, emit them in signals, etc. - New methodbus_g_connection_open provides a way to open connections to an arbitrary address - Various bugs and memory leaks fixed
2006-08-23 11:45:16 +02:00
BUILDLINK_ABI_DEPENDS.dbus-glib+= dbus-glib>=0.71
Initial import of dbus-glib, version 0.22: D-BUS is a message bus, used for sending messages between applications. Conceptually, it fits somewhere in between raw sockets and CORBA in terms of complexity. D-BUS supports broadcast messages, asynchronous messages (thus decreasing latency), authentication, and more. It is designed to be low-overhead; messages are sent using a binary protocol, not using XML. D-BUS also supports a method call mapping for its messages, but it is not required; this makes using the system quite simple. This package provides the D-BUS interface to GLib and the dbus-monitor utility (included here because it also uses GLib).
2004-10-11 19:46:41 +02:00
BUILDLINK_PKGSRCDIR.dbus-glib?= ../../sysutils/dbus-glib
.endif # DBUS_GLIB_BUILDLINK3_MK
.include "../../devel/glib2/buildlink3.mk"
Include dbus's buildlink3.mk file (needed at build-time, specially because of the dbus.pc file).
2005-03-16 22:14:46 +01:00
.include "../../sysutils/dbus/buildlink3.mk"
Initial import of dbus-glib, version 0.22: D-BUS is a message bus, used for sending messages between applications. Conceptually, it fits somewhere in between raw sockets and CORBA in terms of complexity. D-BUS supports broadcast messages, asynchronous messages (thus decreasing latency), authentication, and more. It is designed to be low-overhead; messages are sent using a binary protocol, not using XML. D-BUS also supports a method call mapping for its messages, but it is not required; this makes using the system quite simple. This package provides the D-BUS interface to GLib and the dbus-monitor utility (included here because it also uses GLib).
2004-10-11 19:46:41 +02:00
.include "../../textproc/expat/buildlink3.mk"
Aligned the last line of the buildlink3.mk files with the first line, so that they look nicer.
2006-04-12 12:26:59 +02:00
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//}
Reference in a new issue Copy permalink