Add a pre-configure rule after all, since it's helpful to be able

to also run a rule before you apply patches and then go into the 3 stage
script configuration.  This bit Adam David in his dgd port.
Submitted by:	jkh
This commit is contained in:
Jordan K. Hubbard 1994-08-25 22:59:56 +00:00
parent d843c3038f
commit 367eafb79a
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=2284

View File

@ -1,7 +1,7 @@
# bsd.port.mk - 940820 Jordan K. Hubbard.
# This file is in the public domain.
#
# $Id: bsd.port.mk,v 1.18 1994/08/25 13:56:08 jkh Exp $
# $Id: bsd.port.mk,v 1.19 1994/08/25 21:02:45 jkh Exp $
#
# Supported Variables and their behaviors:
@ -18,6 +18,7 @@
# PKGDIR - Package creation files.
#
# USE_GMAKE - Says that the package uses gmake.
# USE_IMAKE - Says that the package uses imake.
# HAS_CONFIGURE - Says that the package has its own configure script.
# CONFIGURE_ARGS - Pass these args to configure, if $HAS_CONFIGURE.
# HOME_LOCATION - site/path name (or user's email address) describing
@ -143,16 +144,16 @@ build: configure pre-build
.endif
.endif
# No pre-configure stuff since that's handled differently. We wrap
# pre-configure and post-configure scripts around what is generally
# an originally-provided script file, and easier to pre/post install for
# than change.
.if !target(pre-configure)
pre-configure:
@echo -n
.endif
.if !target(configure)
# This is done with a .configure because configures are often expensive,
# and you don't want it done again gratuitously when you're trying to get
# a make of the whole tree to work.
configure: extract ${CONFIGURE_COOKIE}
configure: pre-configure extract ${CONFIGURE_COOKIE}
${CONFIGURE_COOKIE}:
@echo "===> Configuring for ${DISTNAME}"