Date: 14 Sep 1998 16:19:21 -0500 From: Don Croyle <croyle@gelemna.ft-wayne.in.us> To: ports@FreeBSD.ORG Subject: Re: ELF style (where to test PORTOBJFORMAT) Message-ID: <86g1dul7dy.fsf@emerson.gelemna.ft-wayne.in.us> In-Reply-To: Zach Heilig's message of "Mon, 14 Sep 1998 08:59:39 -0500" References: <19980914085939.A9766@znh.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Zach Heilig <zach@gaffaneys.com> writes:
> Typically, in a port makefile, the very last line is
>
> .include <bsd.port.mk>
>
> Obviously, since <bsd.port.mk> sets PORTOBJFORMAT, you cannot test that
> variable before the .include, so is it good style to have lines after the
> .include? Or, is PORTOBJFORMAT not for consumption in the top level makefile.
Within a target, some testing indcates that a shell construct like:
test:
if [ "${PORTOBJFORMAT}" = "elf" ]; then\
${ECHO} "elf";\
else\
${ECHO} "aout";\
fi
is safe and will yield the expected results.
I don't see any way to use PORTOBJFORMAT in an .if construct other
than by putting it below the .include.
--
I've always wanted to be a dilettante, but I've never quite been ready
to make the commitment.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86g1dul7dy.fsf>