From 34d11d8a0f59e1c62bc5b1cc1046d3275e061062 Mon Sep 17 00:00:00 2001 From: jlam Date: Sat, 23 Jun 2001 19:26:48 +0000 Subject: Generalize how the dependency pattern may be specified. Instead of just FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib. Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS. --- comms/pilot-link/buildlink.mk | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'comms/pilot-link') diff --git a/comms/pilot-link/buildlink.mk b/comms/pilot-link/buildlink.mk index ccca3651816..57184fd657d 100644 --- a/comms/pilot-link/buildlink.mk +++ b/comms/pilot-link/buildlink.mk @@ -1,10 +1,11 @@ -# $NetBSD: buildlink.mk,v 1.1 2001/06/22 05:49:42 jlam Exp $ +# $NetBSD: buildlink.mk,v 1.2 2001/06/23 19:26:50 jlam Exp $ # # This Makefile fragment is included by packages that use pilot-link. # # To use this Makefile fragment, simply: # -# (1) Optionally define PILOT_LINK_REQD to the version of pilot-link desired. +# (1) Optionally define BUILDLINK_DEPENDS.pilot-link to the dependency pattern +# for the version of pilot-link desired. # (2) Include this Makefile fragment in the package Makefile, # (3) Add ${BUILDLINK_DIR}/include to the front of the C preprocessor's header # search path, and @@ -14,8 +15,8 @@ .if !defined(PILOT_LINK_BUILDLINK_MK) PILOT_LINK_BUILDLINK_MK= # defined -PILOT_LINK_REQD?= 0.9.3 -DEPENDS+= pilot-link>=${PILOT_LINK_REQD}:../../comms/pilot-link +BUILDLINK_DEPENDS.pilot-link?= pilot-link>=0.9.3 +DEPENDS+= ${BUILDLINK_DEPENDS.pilot-link}:../../comms/pilot-link BUILDLINK_PREFIX.pilot-link= ${LOCALBASE} BUILDLINK_FILES.pilot-link= include/pi-*.* -- cgit v1.2.3