1 Dec 2005 01:52
Re: proposal of how to deal with missing header files supplied by nbcompat
Roland Illig <roland.illig <at> gmx.de>
2005-12-01 00:52:45 GMT
2005-12-01 00:52:45 GMT
Georg Schwarz wrote:
> In Addition, PLIST would have an extra entry
>
> ${NEED_REGEX_H}include/regex.h
>
> libnbcompat's Makefile would finally need
>
> .if defined(NEED_REGEX_H) && !empty(NEED_REGEX_H:M[Yy][Ee][Ss])
> PLIST_SUBST+= NEED_REGEX_H=
> .else
> PLIST_SUBST+= NEED_REGEX_H=" <at> comment "
> .endif
It's not specific to this thread, but I would like the PLIST "variables"
to have a certain naming convention. NEED_REGEX_H is fine for Makefiles,
but in PLIST I'd like it to be called IF_NEED_REGEX_H:
${IF_NEED_REGEX_H}include/regex.h
To me, this just _sounds_ good when reading it aloud. :)
> A package requiring, say, regex.h and fnmatch.h would get some code like
> this:
>
> .if (defined(NEED_REGEX_H) && !empty(NEED_REGEX_H:M[Yy][Ee][Ss])) \
> || (defined(NEED_FNMATCH_H) && !empty(NEED_FNMATCH_H:M[Yy][Ee][Ss]))
> .include "../../pkgtools/libnbcompat/buildlink3.mk"
> .endif
This looks quite ugly, although it is straight-forward. We are going to
(Continue reading)
RSS Feed