kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/libdfui/buildlink3.mk

22 lines
618 B
Makefile
Raw Normal View History

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
# $NetBSD: buildlink3.mk,v 1.7 2006/07/08 23:10:44 jlam Exp $
Initial import of libdfui-3.0. libdfui is a LIBrary for DragonFly User Interfaces. It provides a highly abstract user interaction interface with which an application program (termed the backend) can communicate with a user via a concreate user interface terminal program (termed the frontend.) The frontend and the backend can communicate over several kinds of transport layers (TCP, CAPS, and Named Pipes.) The protocol is abstract enough so that the frontend can occupy nearly any medium (GUI, addressable text console, teletype, voice synthesis/recognition, etc) with little to no `fudging' of the semantics (i.e. the structure and nature of the information that the backend wishes to present and/or acquire.)
2005-02-09 06:41:35 +01:00
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+
LIBDFUI_BUILDLINK3_MK:= ${LIBDFUI_BUILDLINK3_MK}+
.if !empty(BUILDLINK_DEPTH:M+)
BUILDLINK_DEPENDS+= libdfui
.endif
BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Nlibdfui}
BUILDLINK_PACKAGES+= libdfui
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}libdfui
Initial import of libdfui-3.0. libdfui is a LIBrary for DragonFly User Interfaces. It provides a highly abstract user interaction interface with which an application program (termed the backend) can communicate with a user via a concreate user interface terminal program (termed the frontend.) The frontend and the backend can communicate over several kinds of transport layers (TCP, CAPS, and Named Pipes.) The protocol is abstract enough so that the frontend can occupy nearly any medium (GUI, addressable text console, teletype, voice synthesis/recognition, etc) with little to no `fudging' of the semantics (i.e. the structure and nature of the information that the backend wishes to present and/or acquire.)
2005-02-09 06:41:35 +01:00
.if !empty(LIBDFUI_BUILDLINK3_MK:M+)
Sync in libdfui-4.2 from pkgsrc-wip.
2006-04-10 16:58:48 +02:00
BUILDLINK_API_DEPENDS.libdfui+= libdfui>=4.1
Initial import of libdfui-3.0. libdfui is a LIBrary for DragonFly User Interfaces. It provides a highly abstract user interaction interface with which an application program (termed the backend) can communicate with a user via a concreate user interface terminal program (termed the frontend.) The frontend and the backend can communicate over several kinds of transport layers (TCP, CAPS, and Named Pipes.) The protocol is abstract enough so that the frontend can occupy nearly any medium (GUI, addressable text console, teletype, voice synthesis/recognition, etc) with little to no `fudging' of the semantics (i.e. the structure and nature of the information that the backend wishes to present and/or acquire.)
2005-02-09 06:41:35 +01:00
BUILDLINK_PKGSRCDIR.libdfui?= ../../devel/libdfui
.endif # LIBDFUI_BUILDLINK3_MK
Fix include path (devel, not wip).
2006-04-10 17:03:29 +02:00
.include "../../devel/libaura/buildlink3.mk"
Initial import of libdfui-3.0. libdfui is a LIBrary for DragonFly User Interfaces. It provides a highly abstract user interaction interface with which an application program (termed the backend) can communicate with a user via a concreate user interface terminal program (termed the frontend.) The frontend and the backend can communicate over several kinds of transport layers (TCP, CAPS, and Named Pipes.) The protocol is abstract enough so that the frontend can occupy nearly any medium (GUI, addressable text console, teletype, voice synthesis/recognition, etc) with little to no `fudging' of the semantics (i.e. the structure and nature of the information that the backend wishes to present and/or acquire.)
2005-02-09 06:41:35 +01:00
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