remove a word which shouldn't be there.
This commit is contained in:
parent
c0725b8798
commit
f8cbf47c3e
1 changed files with 3 additions and 3 deletions
|
@ -1,4 +1,4 @@
|
|||
$NetBSD: BUILDLINK3_DG,v 1.3 2004/02/05 08:50:38 jlam Exp $
|
||||
$NetBSD: BUILDLINK3_DG,v 1.4 2004/05/08 23:46:20 grant Exp $
|
||||
|
||||
0 Developer's guide to buildlink3
|
||||
=================================
|
||||
|
@ -44,7 +44,7 @@ into native toolchain equivalents.
|
|||
|
||||
buildlink3.mk files have two major differences over buildlink2.mk
|
||||
files. The first, most noticeable difference is that buildlink3.mk
|
||||
generally don't have contain a BUILDLINK_FILES definition. This is
|
||||
generally don't contain a BUILDLINK_FILES definition. This is
|
||||
because buildlink3 automatically determines which files to symlink
|
||||
into ${BUILDLINK_DIR} by examining the PLIST of the installed package.
|
||||
The second difference is that buildlink3.mk files keep track of how
|
||||
|
@ -92,7 +92,7 @@ The following real-life example buildlink3.mk is taken from
|
|||
graphics/tiff:
|
||||
|
||||
------------8<------------8<------------8<------------8<------------
|
||||
# $NetBSD: BUILDLINK3_DG,v 1.3 2004/02/05 08:50:38 jlam Exp $
|
||||
# $NetBSD: BUILDLINK3_DG,v 1.4 2004/05/08 23:46:20 grant Exp $
|
||||
|
||||
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+
|
||||
TIFF_BUILDLINK3_MK:= ${TIFF_BUILDLINK3_MK}+
|
||||
|
|
Loading…
Reference in a new issue