Subject: Re: Handling options in bl3 files
To: Mark Davies <mark@mcs.vuw.ac.nz>
From: Dieter Baron <dillo@danbala.tuwien.ac.at>
List: tech-pkg
Date: 06/01/2005 17:22:16
In article <200506020301.55567.mark@mcs.vuw.ac.nz> Mark wrote:
: On Thursday 02 June 2005 02:51, Thomas Klausner wrote:
: > Yes, but the details matter here.
: > What should the bl3 file include so that the PKG_OPTIONS.allegro
: > are defined correctly?
: kdelibs3/buildlink3.mk has this fragment in it that jlam did:
: .if !defined(PKG_BUILD_OPTIONS.kdelibs)
: PKG_BUILD_OPTIONS.kdelibs!= \
: cd ${BUILDLINK_PKGSRCDIR.kdelibs} && \
: ${MAKE} show-var ${MAKEFLAGS} VARNAME=PKG_OPTIONS
: MAKEFLAGS+= PKG_BUILD_OPTIONS.kdelibs=${PKG_BUILD_OPTIONS.kdelibs:Q}
: .endif
: MAKEVARS+= PKG_BUILD_OPTIONS.kdelibs
: .if !empty(PKG_BUILD_OPTIONS.kdelibs:Mcups)
: . include "../../print/cups/buildlink3.mk"
: .endif
: so something like that I presume.
If kdelibs is already installed, the options used to compile the
installed package should be used, not the current option settings:
PKG_BUILD_OPTIONS.kdelibs!= \
pkg_info -B kdelibs | sed -n 's/^PKG_OPTIONS=[ ]*//p'
yours,
dillo