blob: 2cc1c5fb7a4c34b6e0c0d7d66221d99fffb0c8df (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
# $NetBSD: buildlink3.mk,v 1.34 2009/07/12 17:23:13 ahoka Exp $
BUILDLINK_TREE+= ncurses
.if !defined(NCURSES_BUILDLINK3_MK)
NCURSES_BUILDLINK3_MK:=
BUILDLINK_API_DEPENDS.ncurses+= ncurses>=5.3nb1
BUILDLINK_ABI_DEPENDS.ncurses+= ncurses>=5.4nb1
BUILDLINK_PKGSRCDIR.ncurses?= ../../devel/ncurses
BUILDLINK_LIBNAME.ncurses= ncurses
BUILDLINK_LDADD.ncurses?= ${BUILDLINK_LIBNAME.ncurses:S/^/-l/:S/^-l$//}
# Many packages expect the ncurses headers and libraries to be usable as
# <curses.h> and -lcurses and they often only look in include/ rather than
# some properly written autoconf macros wich also try to puck up
# ncurses/ncurses.h.
#
BUILDLINK_TARGETS+= buildlink-ncurses-curses-h buildlink-ncurses-ncurses-h
BUILDLINK_TRANSFORM+= l:curses:${BUILDLINK_LIBNAME.ncurses}
.PHONY: buildlink-ncurses-curses-h buildlink-ncurses-ncurses-h
buildlink-ncurses-curses-h:
${RUN} \
src=${BUILDLINK_PREFIX.ncurses:Q}"/include/ncurses/curses.h"; \
dest=${BUILDLINK_DIR:Q}"/include/curses.h"; \
if ${TEST} ! -f "$$dest" -a -f "$$src"; then \
${ECHO_BUILDLINK_MSG} "Linking ncurses/curses.h -> curses.h."; \
${MKDIR} `${DIRNAME} "$$dest"`; \
${LN} -s "$$src" "$$dest"; \
fi
buildlink-ncurses-ncurses-h:
${RUN} \
src=${BUILDLINK_PREFIX.ncurses:Q}"/include/ncurses/ncurses.h"; \
dest=${BUILDLINK_DIR:Q}"/include/ncurses.h"; \
if ${TEST} ! -f "$$dest" -a -f "$$src"; then \
${ECHO_BUILDLINK_MSG} "Linking ncurses/ncurses.h -> ncurses.h.";\
${MKDIR} `${DIRNAME} "$$dest"`; \
${LN} -s "$$src" "$$dest"; \
fi
.endif # NCURSES_BUILDLINK3_MK
BUILDLINK_TREE+= -ncurses
|
