tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CONFIGURE_ARGS in mk/x11.buildlink3.mk
On Tue, 08 Jul 2008 20:54:03 +0900, Joerg Sonnenberger
<joerg%britannica.bec.de@localhost> wrote:
> On Mon, Jul 07, 2008 at 11:40:20AM +0900, OBATA Akio wrote:
>> On Mon, 07 Jul 2008 04:06:14 +0900, Joerg Sonnenberger
>> <joerg%britannica.bec.de@localhost> wrote:
>>
>> >> And if exists, do those packages need like a following settings?
>> >>
>> >> .if ${X11_TYPE} == "modular"
>> >> CONFIGURE_ARGS+= --x-includes=${X11BASE:Q}/include
>> >> CONFIGURE_ARGS+= --x-libraries=${X11BASE:Q}/lib
>> >> .endif
>> >
>> > Please use ${PREFIX}. But yes, this is otherwise fine.
>> > See x11/multi-aterm for an existing case.
>>
>> How about platforms using builtin libX11 (MacOS X?) ?
>
> In that case it should be BUILDLINK_PREFIX :) Not sure if it matters at
> all, this is just to workaround a stupid configure test.
How about following code? OK?
.include "../x11/libX11/buildlink3.mk"
.if !defined(_X11_BUILDLINK3_MK)
CONFIGURE_ARGS+= --x-includes=${BUILDLINK_PREFIX.libX11:Q}/include
CONFIGURE_ARGS+= --x-libraries=${BUILDLINK_PREFIX.libX11:Q}/lib
.endif
--
"Of course I love NetBSD":-)
OBATA Akio / obache%NetBSD.org@localhost
Home |
Main Index |
Thread Index |
Old Index