Subject: Re: Handling options in bl3 files
To: Thomas Klausner <wiz@NetBSD.org>
From: Johnny C. Lam <jlam@NetBSD.org>
Date: 06/01/2005 12:09:25
Thomas Klausner wrote:
> While trying to convert devel/allegro to the options
> framework, I stumbled over the following problem:
> Its bl3.mk file has contains
> .if !empty(USE_ESOUND:M[Yy][Ee][Ss])
> . include "../../audio/esound/buildlink3.mk"
> which should be convert to match against the PKG_OPTIONS
> of the (to-be-) installed package.
> How should this be done?
One example of this is devel/apr/buildlink3.mk. It simply checks what
the package's options would be if it was built from scratch. I am
eventually going to turn this into a check of the PKG_OPTIONS of the
installed package, but there are some other infrastructure changes that
need to be made first having to deal with the order in which steps are
-- Johnny Lam <jlam@NetBSD.org>