mirror/freebsd
1
0
Fork 0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-17 10:26:15 +00:00
Code Issues Releases Activity
0bdb7528db
freebsd/share/mk/bsd.port.mk

685 lines
20 KiB
Makefile
Raw Normal View History

Eliminate a few lurking bogons - this is almost close to being right!
1994-09-11 12:01:05 +00:00
# -*- mode: Fundamental; tab-width: 4; -*-
#
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
# bsd.port.mk - 940820 Jordan K. Hubbard.
# This file is in the public domain.
#
Change the xmkmf call to a xmkmf -a call. This should be more correct for all X11R5 and X11R6 ports. This is the way how it should be normally used according the manuals. Only pre-X1R5 ( X11R4, X11R3) ports can't handle it.
1995-03-19 12:49:06 +00:00
# $Id: bsd.port.mk,v 1.116 1995/03/03 07:42:10 jkh Exp $
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
#
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# Please view me with 4 column tabs!
Eliminate a few lurking bogons - this is almost close to being right!
1994-09-11 12:01:05 +00:00
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
# Supported Variables and their behaviors:
#
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# Variables that typically apply to all ports:
#
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# PORTSDIR - The root of the ports tree (default: /usr/ports).
# DISTDIR - Where to get gzip'd, tarballed copies of original sources
# (default: ${PORTSDIR}/distfiles).
Add PREFIX pointing to ${DESTDIR}/usr/local - let's see if we can't make an entire system work nicely with DESTDIR (to say nothing of being able to move from /usr/local to somewhere else).
1994-10-04 14:44:56 +00:00
# PREFIX - Where to install things in general (default: /usr/local).
Adjust comments to document MASTER_SITES and remove mention of HOME_LOCATION.
1994-09-13 06:43:10 +00:00
# MASTER_SITES - Primary location(s) for distribution files if not found
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# locally (default:
# ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles)
#
2 new concepts that just occurred to me: MASTER_SITE_OVERRIDE - If set in the environment, will override everyone's MASTER_SITES settings. Useful if you'd prefer to point to a distfiles repository somewhere closer. MASTER_SITE_FREEBSD - Sets OVERRIDE to be FreeBSD's own master repository.
1994-11-17 00:18:28 +00:00
# MASTER_SITE_OVERRIDE - If set, override the MASTER_SITES setting with this
# value.
# MASTER_SITE_FREEBSD - If set, only use the FreeBSD master repository for
# MASTER_SITES.
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# PACKAGES - A top level directory where all packages go (rather than
# going locally to each port). (default: ${PORTSDIR}/packages).
# GMAKE - Set to path of GNU make if not in $PATH (default: gmake).
Change the xmkmf call to a xmkmf -a call. This should be more correct for all X11R5 and X11R6 ports. This is the way how it should be normally used according the manuals. Only pre-X1R5 ( X11R4, X11R3) ports can't handle it.
1995-03-19 12:49:06 +00:00
# XMKMF - Set to path of `xmkmf' if not in $PATH (default: xmkmf -a ).
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
#
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# Variables that typically apply to an individual port. Non-Boolean
# variables without defaults are *mandatory*.
#
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
#
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# WRKDIR - A temporary working directory that gets *clobbered* on clean
# (default: ${.CURDIR}/work).
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# WRKSRC - A subdirectory of ${WRKDIR} where the distribution actually
# unpacks to. (Default: ${WRKDIR}/${DISTNAME} unless
# NO_WRKSUBDIR is set, in which case simply ${WRKDIR}).
# DISTNAME - Name of port or distribution.
# DISTFILES - Name(s) of archive file(s) containing distribution
# (default: ${DISTDIR}/${DISTNAME}${EXTRACT_SUFX}).
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
# PKGNAME - Name of the package file to create if the DISTNAME
# isn't really relevant for the port/package
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# (default: ${DISTNAME}).
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
# EXTRACT_ONLY - If defined, a subset of ${DISTFILES} you want to
# actually extract.
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# PATCHDIR - A directory containing any required patches
# (default: ${.CURDIR}/patches)
Typo fix from Ollivier Robert. Submitted by: ollivier
1995-01-05 02:15:05 +00:00
# SCRIPTDIR - A directory containing any auxiliary scripts
# (default: ${.CURDIR}/scripts)
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# FILESDIR - A directory containing any miscellaneous additional files.
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# (default: ${.CURDIR}/files)
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# PKGDIR - A direction containing any package creation files.
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# (default: ${.CURDIR}/pkg)
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
#
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# NO_EXTRACT - Use a dummy (do-nothing) extract target.
# NO_CONFIGURE - Use a dummy (do-nothing) configure target.
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# NO_BUILD - Use a dummy (do-nothing) build target.
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# NO_PACKAGE - Use a dummy (do-nothing) package target.
# NO_INSTALL - Use a dummy (do-nothing) install target.
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
# NO_WRKSUBDIR - Assume port unpacks directly into ${WRKDIR}.
Add support for NO_WRKDIR.
1994-11-17 00:25:16 +00:00
# NO_WRKDIR - There's no work directory at all; port does this someplace
# else.
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
# NO_DEPENDS - Don't verify build of dependencies.
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# USE_GMAKE - Says that the port uses gmake.
# USE_IMAKE - Says that the port uses imake.
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
# NO_INSTALL_MANPAGES - For imake ports that don't like the install.man
Erk. Damn. A hash perfixing a comment was lost somewhere. Fixed.
1994-12-11 14:12:30 +00:00
# target.
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# HAS_CONFIGURE - Says that the port has its own configure script.
If GNU_CONFIGURE is set, pass `--prefix=${PREFIX}'; this should help at least the GNU ports play nice with PREFIX.
1994-10-04 15:44:03 +00:00
# GNU_CONFIGURE - Set if you are using GNU configure (optional).
Allow arbitrarily named configure script for use w/ HAS_CONFIGURE.
1995-02-06 08:52:19 +00:00
# CONFIGURE_SCRIPT - Name of configure script, defaults to 'configure'.
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# CONFIGURE_ARGS - Pass these args to configure, if ${HAS_CONFIGURE} set.
Add new IS_INTERACTIVE flag. This lets you specify that the port is an interactive port, and requires user input somewhere along the way (either fetching, configuring, building or installing). If the user then sets BATCH in their environment, this port will be skipped. If the user sets INTERACTIVE, then ONLY those ports marked interactive are run (allowing one to do all ports in two passes). If the user sets both BATCH and INTERACTIVE, then a metal claw extends from the CRT and brutally yanks their nose off.
1994-10-14 07:56:46 +00:00
# IS_INTERACTIVE - Set this if your port needs to interact with the user
Some of the doc here was less than adequately fleshed-out. Make some feeble attempt to do so.
1995-01-04 08:30:33 +00:00
# during a build. User can then decide to skip this port by
# setting ${BATCH}, or compiling only the interactive ports
# by setting ${INTERACTIVE}.
Add long-awaited (:) support for sophisticated dependency checking. We now have three variables: EXEC_DEPENDS - A list of "prog:dir" pairs of other ports this package depends on. "prog" is the name of an executable. make will search your $PATH for it and go into "dir" to do a "make all install" if it's not found. LIB_DEPENDS - A list of "lib:dir" pairs of other ports this package depends on. "lib" is the name of a shared library. make will use "ldconfig -r" to search for the library. Note that lib can be any regular expression, and you need two backslashes in front of dots (.) to supress its special meaning (e.g., use "foo\\.2\\.:${PORTSDIR}/utils/foo" to match "libfoo.2.*"). DEPENDS - A list of other ports this package depends on being made first. Use this for things that don't fall into the above two categories. DEPENDS behaves exactly like before, so old Makefiles will still work the same. The two variables are lists of pairs as described above. For instance, if your program depends on unzip and libjpeg.5.*, use the following definitions: EXEC_DEPENDS= unzip:${PORTSDIR}/archivers/unzip LIB_DEPENDS= jpeg\\.5\\.:${PORTSDIR}/graphics/jpeg gmake:${PORTSDIR}/utils/gmake is automatically added to EXEC_DEPENDS if USE_GMAKE is defined. If NO_DEPENDS is defined, the list will just be printed out one by one.
1995-02-04 05:49:26 +00:00
# EXEC_DEPENDS - A list of "prog:dir" pairs of other ports this
# package depends on. "prog" is the name of an
# executable. make will search your $PATH for it and go
# into "dir" to do a "make all install" if it's not found.
# LIB_DEPENDS - A list of "lib:dir" pairs of other ports this package
# depends on. "lib" is the name of a shared library.
# make will use "ldconfig -r" to search for the
# library. Note that lib can be any regular expression,
# and you need two backslashes in front of dots (.) to
# supress its special meaning (e.g., use
# "foo\\.2\\.:${PORTSDIR}/utils/foo" to match "libfoo.2.*").
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# DEPENDS - A list of other ports this package depends on being
Add long-awaited (:) support for sophisticated dependency checking. We now have three variables: EXEC_DEPENDS - A list of "prog:dir" pairs of other ports this package depends on. "prog" is the name of an executable. make will search your $PATH for it and go into "dir" to do a "make all install" if it's not found. LIB_DEPENDS - A list of "lib:dir" pairs of other ports this package depends on. "lib" is the name of a shared library. make will use "ldconfig -r" to search for the library. Note that lib can be any regular expression, and you need two backslashes in front of dots (.) to supress its special meaning (e.g., use "foo\\.2\\.:${PORTSDIR}/utils/foo" to match "libfoo.2.*"). DEPENDS - A list of other ports this package depends on being made first. Use this for things that don't fall into the above two categories. DEPENDS behaves exactly like before, so old Makefiles will still work the same. The two variables are lists of pairs as described above. For instance, if your program depends on unzip and libjpeg.5.*, use the following definitions: EXEC_DEPENDS= unzip:${PORTSDIR}/archivers/unzip LIB_DEPENDS= jpeg\\.5\\.:${PORTSDIR}/graphics/jpeg gmake:${PORTSDIR}/utils/gmake is automatically added to EXEC_DEPENDS if USE_GMAKE is defined. If NO_DEPENDS is defined, the list will just be printed out one by one.
1995-02-04 05:49:26 +00:00
# made first. Use this for things that don't fall into
# the above two categories.
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
# EXTRACT_CMD - Command for extracting archive (default: tar).
# EXTRACT_SUFX - Suffix for archive names (default: .tar.gz).
# EXTRACT_ARGS - Arguments to ${EXTRACT_CMD} (default: -C ${WRKDIR} -xzf).
#
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# NCFTP - Full path to ncftp command if not in $PATH (default: ncftp).
Change wrong comment: NCFTP_ARGS --> NCFTPFLAGS
1994-11-25 17:04:02 +00:00
# NCFTPFLAGS - Arguments to ${NCFTP} (default: -N).
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
#
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
#
# Default targets and their behaviors:
#
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# fetch - Retrieves ${DISTFILES} into ${DISTDIR} as necessary.
# extract - Unpacks ${DISTFILES} into ${WRKDIR}.
# configure - Applies patches, if any, and runs either GNU configure, one
# or more local configure scripts or nothing, depending on
# what's available.
2 new concepts that just occurred to me: MASTER_SITE_OVERRIDE - If set in the environment, will override everyone's MASTER_SITES settings. Useful if you'd prefer to point to a distfiles repository somewhere closer. MASTER_SITE_FREEBSD - Sets OVERRIDE to be FreeBSD's own master repository.
1994-11-17 00:18:28 +00:00
# patch - Apply any provided patches to the source.
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
# build - Actually compile the sources.
# install - Install the results of a build.
Add reinstall target for Poul-H. This lets you install again from the same build, ignoring the INSTALL_COOKIE.
1994-11-03 19:14:08 +00:00
# reinstall - Install the results of a build, ignoring "already installed"
# flag.
Set PREFIX in the build target. Suggested by John Fieber.
1995-01-23 18:22:36 +00:00
# package - Create a package from an _installed_ port.
Document describe target.
1995-01-04 07:35:46 +00:00
# describe - Try to generate a one-line description for each port for
# use in INDEX files and the like.
Gary Palmer's patches for checksumming and description. Submitted by: gpalmer
1995-01-04 23:06:38 +00:00
# checksum - Use files/md5 to ensure that your distfiles are valid
Set PREFIX in the build target. Suggested by John Fieber.
1995-01-23 18:22:36 +00:00
# makesum - Generate files/md5 (only do this for your own ports!)
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
#
# Default sequence for "all" is: fetch extract configure build
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.if exists(${.CURDIR}/../Makefile.inc)
.include "${.CURDIR}/../Makefile.inc"
.endif
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
# These need to be absolute since we don't know how deep in the ports
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# tree we are and thus can't go relative. They can, of course, be overridden
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
# by individual Makefiles.
DESTDIR added to PORTSDIR definition
1994-09-19 00:41:03 +00:00
PORTSDIR?= ${DESTDIR}/usr/ports
I found today that making packages for X11 ports wasn't working. Further investigation showed that prefix was erroneously set to /usr/local for X11 based ports as well, when the assumption was that they'd really go into ${X11BASE} (an /etc/make.conf variable that the user's free to set). Set X11BASE to /usr/X11R6 if the user hasn't already, and assume that the user really wants prefix to point there when the port is XMKMF based.
1994-11-17 10:06:03 +00:00
X11BASE?= /usr/X11R6
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
DISTDIR?= ${PORTSDIR}/distfiles
PACKAGES?= ${PORTSDIR}/packages
Add support for NO_WRKDIR.
1994-11-17 00:25:16 +00:00
.if !defined(NO_WRKDIR)
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
WRKDIR?= ${.CURDIR}/work
Add support for NO_WRKDIR.
1994-11-17 00:25:16 +00:00
.else
WRKDIR?= ${.CURDIR}
.endif
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
.if defined(NO_WRKSUBDIR)
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
WRKSRC?= ${WRKDIR}
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
.else
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
WRKSRC?= ${WRKDIR}/${DISTNAME}
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
.endif
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
PATCHDIR?= ${.CURDIR}/patches
SCRIPTDIR?= ${.CURDIR}/scripts
FILESDIR?= ${.CURDIR}/files
PKGDIR?= ${.CURDIR}/pkg
Whoops! Typo. Correct.
1994-11-17 10:07:45 +00:00
.if defined(USE_IMAKE)
I found today that making packages for X11 ports wasn't working. Further investigation showed that prefix was erroneously set to /usr/local for X11 based ports as well, when the assumption was that they'd really go into ${X11BASE} (an /etc/make.conf variable that the user's free to set). Set X11BASE to /usr/X11R6 if the user hasn't already, and assume that the user really wants prefix to point there when the port is XMKMF based.
1994-11-17 10:06:03 +00:00
PREFIX?= ${X11BASE}
.else
PREFIX?= /usr/local
.endif
Automatically add gmake to DEPENDS, if USE_GMAKE
1994-12-17 02:37:26 +00:00
.if defined(USE_GMAKE)
Add long-awaited (:) support for sophisticated dependency checking. We now have three variables: EXEC_DEPENDS - A list of "prog:dir" pairs of other ports this package depends on. "prog" is the name of an executable. make will search your $PATH for it and go into "dir" to do a "make all install" if it's not found. LIB_DEPENDS - A list of "lib:dir" pairs of other ports this package depends on. "lib" is the name of a shared library. make will use "ldconfig -r" to search for the library. Note that lib can be any regular expression, and you need two backslashes in front of dots (.) to supress its special meaning (e.g., use "foo\\.2\\.:${PORTSDIR}/utils/foo" to match "libfoo.2.*"). DEPENDS - A list of other ports this package depends on being made first. Use this for things that don't fall into the above two categories. DEPENDS behaves exactly like before, so old Makefiles will still work the same. The two variables are lists of pairs as described above. For instance, if your program depends on unzip and libjpeg.5.*, use the following definitions: EXEC_DEPENDS= unzip:${PORTSDIR}/archivers/unzip LIB_DEPENDS= jpeg\\.5\\.:${PORTSDIR}/graphics/jpeg gmake:${PORTSDIR}/utils/gmake is automatically added to EXEC_DEPENDS if USE_GMAKE is defined. If NO_DEPENDS is defined, the list will just be printed out one by one.
1995-02-04 05:49:26 +00:00
EXEC_DEPENDS+= gmake:${PORTSDIR}/devel/gmake
Automatically add gmake to DEPENDS, if USE_GMAKE
1994-12-17 02:37:26 +00:00
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
Eliminate a few lurking bogons - this is almost close to being right!
1994-09-11 12:01:05 +00:00
.if exists(${PORTSDIR}/../Makefile.inc)
.include "${PORTSDIR}/../Makefile.inc"
.endif
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
# Change these if you'd prefer to keep the cookies someplace else.
change COOKIE directory from .CURDIR to WRKDIR since a user may not have write permission to .CURDIR but write permission to WRKDIR. Also, WRKDIR may be deleted and cookie still exist in CURDIR.
1994-09-22 07:45:30 +00:00
EXTRACT_COOKIE?= ${WRKDIR}/.extract_done
CONFIGURE_COOKIE?= ${WRKDIR}/.configure_done
Prevent duplicate installs with an install cookie. Make DEPENDS now does a `make is_depended' in the target port. This defaults to `all install' globally, but can be overriden locally by a port if it wants to do different things when other ports depend on it.
1994-10-03 14:38:27 +00:00
INSTALL_COOKIE?= ${WRKDIR}/.install_done
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
BUILD_COOKIE?= ${WRKDIR}/.build_done
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
PATCH_COOKIE?= ${WRKDIR}/.patch_done
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# How to do nothing. Override if you, for some strange reason, would rather
# do something.
DO_NADA?= echo -n
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
# Miscellaneous overridable commands:
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
GMAKE?= gmake
Change the xmkmf call to a xmkmf -a call. This should be more correct for all X11R5 and X11R6 ports. This is the way how it should be normally used according the manuals. Only pre-X1R5 ( X11R4, X11R3) ports can't handle it.
1995-03-19 12:49:06 +00:00
XMKMF?= xmkmf -a
Use absolute path to md5 program. It lives in /sbin and people are unlikely to have $PATH to it.
1995-02-04 22:56:28 +00:00
MD5?= /sbin/md5
Early md5-checksumming code. This seems to work fine on my machine but needs more testing on more ports than I have on my box.
1994-12-11 20:36:12 +00:00
MD5_FILE?= ${FILESDIR}/md5
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
MAKE_FLAGS?= -f
MAKEFILE?= Makefile
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
NCFTP?= ncftp
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
NCFTPFLAGS?= -N
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
TOUCH?= touch
TOUCH_FLAGS?= -f
Don't hardcode patch and its arguments. Not quite the same patch as submitted by Robert Withrow, but he prodded me into thinking about it again. Thanks, Rob.
1994-09-28 14:19:30 +00:00
PATCH?= patch
PATCH_STRIP?= -p0
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
.if defined(PATCH_DEBUG)
PATCH_ARGS?= -d ${WRKSRC} -E ${PATCH_STRIP}
.else
PATCH_ARGS?= -d ${WRKSRC} --forward --quiet -E ${PATCH_STRIP}
.endif
Don't hardcode patch and its arguments. Not quite the same patch as submitted by Robert Withrow, but he prodded me into thinking about it again. Thanks, Rob.
1994-09-28 14:19:30 +00:00
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
EXTRACT_CMD?= tar
EXTRACT_SUFX?= .tar.gz
Always go to ${WRKDIR} before extraction. Modify the tar extract command args to take advantage of this. Pointed-out-by: asami
1995-02-17 08:52:55 +00:00
EXTRACT_ARGS?= -xzf
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
PKG_CMD?= pkg_create
Add an install prefix for packages, so that they're built by default to track ${PREFIX} (this will override the PLIST prefix).
1994-10-04 15:50:43 +00:00
PKG_ARGS?= -v -c ${PKGDIR}/COMMENT -d ${PKGDIR}/DESCR -f ${PKGDIR}/PLIST -p ${PREFIX}
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
PKG_SUFX?= .tgz
Make package target a lot more general. Submitted by: jkh
1994-08-22 13:11:32 +00:00
For submakes, don't do a `${MAKE} ${MAKEFILE} all' or `${MAKE} ${MAKEFILE} install', indirect the target through ALL_TARGET and INSTALL_TARGET now, so they can be easily overridden.
1994-11-03 19:53:46 +00:00
ALL_TARGET?= all
INSTALL_TARGET?= install
2 new concepts that just occurred to me: MASTER_SITE_OVERRIDE - If set in the environment, will override everyone's MASTER_SITES settings. Useful if you'd prefer to point to a distfiles repository somewhere closer. MASTER_SITE_FREEBSD - Sets OVERRIDE to be FreeBSD's own master repository.
1994-11-17 00:18:28 +00:00
.if defined(MASTER_SITE_FREEBSD)
MASTER_SITE_OVERRIDE= ftp://freebsd.cdrom.com/pub/FreeBSD/FreeBSD-current/ports/distfiles/
.endif
Ok, I think I have this whole HOME_LOCATION / MASTER_SITE stuff resolved to a reasonable compromise: MASTER_SITES now contains a space seperated list of sites for which each DISTFILE may be retrieved. This should be a directory spec, which will be concatenated with each file in DISTFILES. HOME_LOCATION is *gone* now and isn't used for anything, so you can delete it from your Makefiles. If you want to force a fetch from a given location, simply do something like: MASTER_SITES= ftp://fnord.foo.bar/pub/dist DISTFILES= a.tar.gz b.tar.gz Your entry in MASTER_SITES will be tried first to fetch a.tar.gz and b.tar.gz, followed by any master sites we have set up (right now, only freebsd.cdrom.com).
1994-09-13 06:22:11 +00:00
# I guess we're in the master distribution business! :) As we gain mirror
# sites for distfiles, add them to this list.
2 new concepts that just occurred to me: MASTER_SITE_OVERRIDE - If set in the environment, will override everyone's MASTER_SITES settings. Useful if you'd prefer to point to a distfiles repository somewhere closer. MASTER_SITE_FREEBSD - Sets OVERRIDE to be FreeBSD's own master repository.
1994-11-17 00:18:28 +00:00
.if !defined(MASTER_SITE_OVERRIDE)
Don't assume / seperator between site name and dist file in fetch.
1994-09-14 15:30:44 +00:00
MASTER_SITES+= ftp://freebsd.cdrom.com/pub/FreeBSD/FreeBSD-current/ports/distfiles/
2 new concepts that just occurred to me: MASTER_SITE_OVERRIDE - If set in the environment, will override everyone's MASTER_SITES settings. Useful if you'd prefer to point to a distfiles repository somewhere closer. MASTER_SITE_FREEBSD - Sets OVERRIDE to be FreeBSD's own master repository.
1994-11-17 00:18:28 +00:00
.else
MASTER_SITES= ${MASTER_SITE_OVERRIDE}
.endif
Geeze, what was I thinking again? Replace all references to: ${DISTDIR}/${DISTNAME}${EXTRACT_SUFX} With simply `${DISTFILE}' which defaults to the above. This lets you easily name distribution files that don't cooperate with any rational naming syntax. Similarly, make a variable called ${PKGFILE} which fills the same purpose for packages. Just trying to make this thing really really general to suit every need. Now I need somebody to figure out how to make the extract target auto-fetch things from ${HOME_LOCATION} with ncftp *if* ncftp is installed and it looks possible to reach the foreign site. That will take some fancy footwork, but would be slick. I've changed this too so that HOME_LOCATION is no longer set by default, allowing you to do an .if defined(..) check for it. The extract rule now does this too. Submitted by: jkh
1994-09-01 16:01:34 +00:00
# Derived names so that they're easily overridable.
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
DISTFILES?= ${DISTNAME}${EXTRACT_SUFX}
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
PKGNAME?= ${DISTNAME}
Start the ball rolling by sticking a MAINTAINER?= line in here. Idea by: jkh@FreeBSD.ORG
1995-02-01 21:47:57 +00:00
MAINTAINER?= FreeBSD-Ports@FreeBSD.ORG
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
.if exists(${PACKAGES})
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
PKGFILE?= ${PACKAGES}/${PKGNAME}${PKG_SUFX}
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
.else
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
PKGFILE?= ${PKGNAME}${PKG_SUFX}
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
Allow arbitrarily named configure script for use w/ HAS_CONFIGURE.
1995-02-06 08:52:19 +00:00
CONFIGURE_SCRIPT?= configure
If GNU_CONFIGURE is set, pass `--prefix=${PREFIX}'; this should help at least the GNU ports play nice with PREFIX.
1994-10-04 15:44:03 +00:00
.if defined(GNU_CONFIGURE)
CONFIGURE_ARGS?= --prefix=${PREFIX}
Also make GNU_CONFIGURE a synonym for HAS_CONFIGURE so you don't have to specify both (looks silly).
1994-10-04 15:48:21 +00:00
HAS_CONFIGURE= yes
If GNU_CONFIGURE is set, pass `--prefix=${PREFIX}'; this should help at least the GNU ports play nice with PREFIX.
1994-10-04 15:44:03 +00:00
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.MAIN: all
Add new IS_INTERACTIVE flag. This lets you specify that the port is an interactive port, and requires user input somewhere along the way (either fetching, configuring, building or installing). If the user then sets BATCH in their environment, this port will be skipped. If the user sets INTERACTIVE, then ONLY those ports marked interactive are run (allowing one to do all ports in two passes). If the user sets both BATCH and INTERACTIVE, then a metal claw extends from the CRT and brutally yanks their nose off.
1994-10-14 07:56:46 +00:00
# If we're in BATCH mode and the port is interactive, or we're in
# interactive mode and the port is non-interactive, skip all the important
# targets. The reason we have two modes is that one might want to leave
# a build in BATCH mode running overnight, then come back in the morning
# and do _only_ the interactive ones that required your intervention.
# This allows you to do both.
#
Back out my previous change. I need to really think about this.
1995-03-03 07:42:10 +00:00
.if (defined(IS_INTERACTIVE) && defined(BATCH)) || (!defined(IS_INTERACTIVE) && defined(INTERACTIVE))
Add new IS_INTERACTIVE flag. This lets you specify that the port is an interactive port, and requires user input somewhere along the way (either fetching, configuring, building or installing). If the user then sets BATCH in their environment, this port will be skipped. If the user sets INTERACTIVE, then ONLY those ports marked interactive are run (allowing one to do all ports in two passes). If the user sets both BATCH and INTERACTIVE, then a metal claw extends from the CRT and brutally yanks their nose off.
1994-10-14 07:56:46 +00:00
all:
@${DO_NADA}
pre-build:
@${DO_NADA}
build:
@${DO_NADA}
pre-install:
@${DO_NADA}
install:
@${DO_NADA}
pre-fetch:
@${DO_NADA}
fetch:
@${DO_NADA}
pre-configure:
@${DO_NADA}
configure:
@${DO_NADA}
.endif
.if !target(all)
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
all: extract configure build
Add new IS_INTERACTIVE flag. This lets you specify that the port is an interactive port, and requires user input somewhere along the way (either fetching, configuring, building or installing). If the user then sets BATCH in their environment, this port will be skipped. If the user sets INTERACTIVE, then ONLY those ports marked interactive are run (allowing one to do all ports in two passes). If the user sets both BATCH and INTERACTIVE, then a metal claw extends from the CRT and brutally yanks their nose off.
1994-10-14 07:56:46 +00:00
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
Prevent duplicate installs with an install cookie. Make DEPENDS now does a `make is_depended' in the target port. This defaults to `all install' globally, but can be overriden locally by a port if it wants to do different things when other ports depend on it.
1994-10-03 14:38:27 +00:00
.if !target(is_depended)
is_depended: all install
.endif
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# The following are used to create easy dummy targets for disabling some
# bit of default target behavior you don't want. They still check to see
# if the target exists, and if so don't do anything, since you might want
# to set this globally for a group of ports in a Makefile.inc, but still
# be able to override from an individual Makefile (since you can't _undefine_
# a variable in make!).
.if defined(NO_EXTRACT) && !target(extract)
extract:
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${EXTRACT_COOKIE}
Gary Palmer's patches for checksumming and description. Submitted by: gpalmer
1995-01-04 23:06:38 +00:00
checksum:
Put dummy targets for make-md5 & check-md5 inside a NO_EXTRACT ifdef so that tcpblast doesn't muck things up
1994-12-17 21:29:38 +00:00
@${DO_NADA}
Gary Palmer's patches for checksumming and description. Submitted by: gpalmer
1995-01-04 23:06:38 +00:00
makesum:
Put dummy targets for make-md5 & check-md5 inside a NO_EXTRACT ifdef so that tcpblast doesn't muck things up
1994-12-17 21:29:38 +00:00
@${DO_NADA}
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
.endif
.if defined(NO_CONFIGURE) && !target(configure)
configure:
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${CONFIGURE_COOKIE}
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
.endif
.if defined(NO_BUILD) && !target(build)
build:
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${BUILD_COOKIE}
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
.endif
.if defined(NO_PACKAGE) && !target(package)
package:
@${DO_NADA}
.endif
.if defined(NO_INSTALL) && !target(install)
install:
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${INSTALL_COOKIE}
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
.endif
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
.if defined(NO_PATCH) && !target(patch)
patch:
@${TOUCH} ${TOUCH_FLAGS} ${PATCH_COOKIE}
.endif
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# More standard targets start here.
Add describe target support.
1995-01-03 11:52:01 +00:00
.if !target(describe)
describe:
Gary Palmer's patches for checksumming and description. Submitted by: gpalmer
1995-01-04 23:06:38 +00:00
.if defined(NO_PACKAGE)
@echo "${.CURDIR}/${DISTNAME}: ** Not packageable";
.else
Add describe target support.
1995-01-03 11:52:01 +00:00
@if [ -f ${PKGDIR}/COMMENT ]; then \
echo "${.CURDIR}/${DISTNAME}: `cat ${PKGDIR}/COMMENT`"; \
else \
echo "${.CURDIR}/${DISTNAME}: ** No Description"; \
fi
.endif
Gary Palmer's patches for checksumming and description. Submitted by: gpalmer
1995-01-04 23:06:38 +00:00
.endif
Add describe target support.
1995-01-03 11:52:01 +00:00
Add reinstall target for Poul-H. This lets you install again from the same build, ignoring the INSTALL_COOKIE.
1994-11-03 19:14:08 +00:00
.if !target(reinstall)
reinstall: pre-reinstall install
pre-reinstall:
@rm -f ${INSTALL_COOKIE}
.endif
Some cosmetic changes. Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
1994-08-24 14:49:33 +00:00
.if !target(pre-install)
pre-install:
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
@${DO_NADA}
Some cosmetic changes. Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
1994-08-24 14:49:33 +00:00
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.if !target(install)
Sort out dependencies. Now they look like: patch: extract configure: depends patch build: configure install: build Does this look ok?
1995-01-05 08:15:53 +00:00
install: build ${INSTALL_COOKIE}
Prevent duplicate installs with an install cookie. Make DEPENDS now does a `make is_depended' in the target port. This defaults to `all install' globally, but can be overriden locally by a port if it wants to do different things when other ports depend on it.
1994-10-03 14:38:27 +00:00
Re-work the way pre-install was being depended. I couldn't make the install cookie work any other way (perhaps I'm just being stupid). In any case, INSTALL_COOKIE now works as advertised, and prevents duplicate installations. pre-install users will have to keep their own cookies if they wish to avoid duplicate installations, or tell me how to make the rules run properly.
1994-10-12 23:32:32 +00:00
${INSTALL_COOKIE}:
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
@echo "===> Installing for ${DISTNAME}"
Add ${.MAKEFLAGS} to sub-makes, pointed by Rod
1994-10-14 21:58:09 +00:00
@${MAKE} ${.MAKEFLAGS} pre-install
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.if defined(USE_GMAKE)
For submakes, don't do a `${MAKE} ${MAKEFILE} all' or `${MAKE} ${MAKEFILE} install', indirect the target through ALL_TARGET and INSTALL_TARGET now, so they can be easily overridden.
1994-11-03 19:53:46 +00:00
@(cd ${WRKSRC}; ${GMAKE} PREFIX=${PREFIX} ${MAKE_FLAGS} ${MAKEFILE} ${INSTALL_TARGET})
Added '${GMAKE} install.man' when installing with Imake and gmake
1994-12-12 22:32:30 +00:00
.if defined(USE_IMAKE) && !defined(NO_INSTALL_MANPAGES)
@(cd ${WRKSRC}; ${GMAKE} ${MAKE_FLAGS} ${MAKEFILE} install.man)
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.else defined(USE_GMAKE)
For submakes, don't do a `${MAKE} ${MAKEFILE} all' or `${MAKE} ${MAKEFILE} install', indirect the target through ALL_TARGET and INSTALL_TARGET now, so they can be easily overridden.
1994-11-03 19:53:46 +00:00
@(cd ${WRKSRC}; ${MAKE} PREFIX=${PREFIX} ${MAKE_FLAGS} ${MAKEFILE} ${INSTALL_TARGET})
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
.if defined(USE_IMAKE) && !defined(NO_INSTALL_MANPAGES)
Invoke install.man if USE_IMAKE is set.
1994-10-22 09:21:35 +00:00
@(cd ${WRKSRC}; ${MAKE} ${MAKE_FLAGS} ${MAKEFILE} install.man)
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.endif
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${INSTALL_COOKIE}
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.endif
Some cosmetic changes. Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
1994-08-24 14:49:33 +00:00
.if !target(pre-package)
pre-package:
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
@${DO_NADA}
Some cosmetic changes. Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
1994-08-24 14:49:33 +00:00
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.if !target(package)
Sigh. I am a hosebrain. I've been using gmake for so long, I've started using some of its features reflexively. Submitted by: jkh
1994-08-25 13:56:08 +00:00
package: pre-package
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
# Makes some gross assumptions about a fairly simple package with no
Make package target a lot more general. Submitted by: jkh
1994-08-22 13:11:32 +00:00
# install, require or deinstall scripts. Override the arguments with
# PKG_ARGS if your package is anything but run-of-the-mill.
Whoops, left out a backslash in my package rule. Submitted by: jkh
1994-08-22 12:00:34 +00:00
@if [ -d ${PKGDIR} ]; then \
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
echo "===> Building package for ${DISTNAME}"; \
${PKG_CMD} ${PKG_ARGS} ${PKGFILE}; \
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
fi
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.endif
Make depends a separate target. Now you can select when the dependency list is traversed.
1994-11-15 10:16:56 +00:00
.if !target(depends)
Add long-awaited (:) support for sophisticated dependency checking. We now have three variables: EXEC_DEPENDS - A list of "prog:dir" pairs of other ports this package depends on. "prog" is the name of an executable. make will search your $PATH for it and go into "dir" to do a "make all install" if it's not found. LIB_DEPENDS - A list of "lib:dir" pairs of other ports this package depends on. "lib" is the name of a shared library. make will use "ldconfig -r" to search for the library. Note that lib can be any regular expression, and you need two backslashes in front of dots (.) to supress its special meaning (e.g., use "foo\\.2\\.:${PORTSDIR}/utils/foo" to match "libfoo.2.*"). DEPENDS - A list of other ports this package depends on being made first. Use this for things that don't fall into the above two categories. DEPENDS behaves exactly like before, so old Makefiles will still work the same. The two variables are lists of pairs as described above. For instance, if your program depends on unzip and libjpeg.5.*, use the following definitions: EXEC_DEPENDS= unzip:${PORTSDIR}/archivers/unzip LIB_DEPENDS= jpeg\\.5\\.:${PORTSDIR}/graphics/jpeg gmake:${PORTSDIR}/utils/gmake is automatically added to EXEC_DEPENDS if USE_GMAKE is defined. If NO_DEPENDS is defined, the list will just be printed out one by one.
1995-02-04 05:49:26 +00:00
depends: exec_depends lib_depends misc_depends
exec_depends:
.if defined(EXEC_DEPENDS)
.if defined(NO_DEPENDS)
# Just print out messages
@for i in ${EXEC_DEPENDS}; do \
prog=`echo $$i | sed -e 's/:.*//'`; \
dir=`echo $$i | sed -e 's/.*://'`; \
echo "===> ${DISTNAME} depends on executable: $$prog ($$dir)"; \
done
.else
@for i in ${EXEC_DEPENDS}; do \
prog=`echo $$i | sed -e 's/:.*//'`; \
dir=`echo $$i | sed -e 's/.*://'`; \
if which -s "$$prog"; then \
echo "===> ${DISTNAME} depends on executable: $$prog - found"; \
else \
echo "===> ${DISTNAME} depends on executable: $$prog - not found"; \
echo "===> Verifying build for $$prog in $$dir"; \
if [ ! -d "$$dir" ]; then \
echo ">> No directory for $$prog. Skipping.."; \
else \
(cd $$dir; ${MAKE} ${.MAKEFLAGS} is_depended) ; \
echo "===> Returning to build of ${DISTNAME}"; \
fi; \
fi; \
done
.endif
.else
@${DO_NADA}
.endif
lib_depends:
.if defined(LIB_DEPENDS)
.if defined(NO_DEPENDS)
# Just print out messages
@for i in ${LIB_DEPENDS}; do \
lib=`echo $$i | sed -e 's/:.*//'`; \
dir=`echo $$i | sed -e 's/.*://'`; \
echo "===> ${DISTNAME} depends on shared library: $$lib ($$dir)"; \
done
.else
@for i in ${LIB_DEPENDS}; do \
lib=`echo $$i | sed -e 's/:.*//'`; \
dir=`echo $$i | sed -e 's/.*://'`; \
if ldconfig -r | grep -q -e "-l$$lib"; then \
echo "===> ${DISTNAME} depends on shared library: $$lib - found"; \
else \
echo "===> ${DISTNAME} depends on shared library: $$lib - not found"; \
echo "===> Verifying build for $$lib in $$dir"; \
if [ ! -d "$$dir" ]; then \
echo ">> No directory for $$lib. Skipping.."; \
else \
(cd $$dir; ${MAKE} ${.MAKEFLAGS} is_depended) ; \
echo "===> Returning to build of ${DISTNAME}"; \
fi; \
fi; \
done
.endif
.else
@${DO_NADA}
.endif
misc_depends:
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
.if defined(DEPENDS)
Make things a little more user-friendly Submitted by: jkh
1994-08-21 17:42:24 +00:00
@echo "===> ${DISTNAME} depends on: ${DEPENDS}"
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
.if !defined(NO_DEPENDS)
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
@for i in ${DEPENDS}; do \
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
echo "===> Verifying build for $$i"; \
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
if [ ! -d $$i ]; then \
echo ">> No directory for $$i. Skipping.."; \
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
else \
Add ${.MAKEFLAGS} to sub-makes, pointed by Rod
1994-10-14 21:58:09 +00:00
(cd $$i; ${MAKE} ${.MAKEFLAGS} is_depended) ; \
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
fi \
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
done
Make things a little more user-friendly Submitted by: jkh
1994-08-21 17:42:24 +00:00
@echo "===> Returning to build of ${DISTNAME}"
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
.endif
Add long-awaited (:) support for sophisticated dependency checking. We now have three variables: EXEC_DEPENDS - A list of "prog:dir" pairs of other ports this package depends on. "prog" is the name of an executable. make will search your $PATH for it and go into "dir" to do a "make all install" if it's not found. LIB_DEPENDS - A list of "lib:dir" pairs of other ports this package depends on. "lib" is the name of a shared library. make will use "ldconfig -r" to search for the library. Note that lib can be any regular expression, and you need two backslashes in front of dots (.) to supress its special meaning (e.g., use "foo\\.2\\.:${PORTSDIR}/utils/foo" to match "libfoo.2.*"). DEPENDS - A list of other ports this package depends on being made first. Use this for things that don't fall into the above two categories. DEPENDS behaves exactly like before, so old Makefiles will still work the same. The two variables are lists of pairs as described above. For instance, if your program depends on unzip and libjpeg.5.*, use the following definitions: EXEC_DEPENDS= unzip:${PORTSDIR}/archivers/unzip LIB_DEPENDS= jpeg\\.5\\.:${PORTSDIR}/graphics/jpeg gmake:${PORTSDIR}/utils/gmake is automatically added to EXEC_DEPENDS if USE_GMAKE is defined. If NO_DEPENDS is defined, the list will just be printed out one by one.
1995-02-04 05:49:26 +00:00
.else
@${DO_NADA}
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
.endif
Add long-awaited (:) support for sophisticated dependency checking. We now have three variables: EXEC_DEPENDS - A list of "prog:dir" pairs of other ports this package depends on. "prog" is the name of an executable. make will search your $PATH for it and go into "dir" to do a "make all install" if it's not found. LIB_DEPENDS - A list of "lib:dir" pairs of other ports this package depends on. "lib" is the name of a shared library. make will use "ldconfig -r" to search for the library. Note that lib can be any regular expression, and you need two backslashes in front of dots (.) to supress its special meaning (e.g., use "foo\\.2\\.:${PORTSDIR}/utils/foo" to match "libfoo.2.*"). DEPENDS - A list of other ports this package depends on being made first. Use this for things that don't fall into the above two categories. DEPENDS behaves exactly like before, so old Makefiles will still work the same. The two variables are lists of pairs as described above. For instance, if your program depends on unzip and libjpeg.5.*, use the following definitions: EXEC_DEPENDS= unzip:${PORTSDIR}/archivers/unzip LIB_DEPENDS= jpeg\\.5\\.:${PORTSDIR}/graphics/jpeg gmake:${PORTSDIR}/utils/gmake is automatically added to EXEC_DEPENDS if USE_GMAKE is defined. If NO_DEPENDS is defined, the list will just be printed out one by one.
1995-02-04 05:49:26 +00:00
Make depends a separate target. Now you can select when the dependency list is traversed.
1994-11-15 10:16:56 +00:00
.endif
.if !target(pre-build)
pre-build:
@${DO_NADA}
.endif
.if !target(build)
Sort out dependencies. Now they look like: patch: extract configure: depends patch build: configure install: build Does this look ok?
1995-01-05 08:15:53 +00:00
build: configure ${BUILD_COOKIE}
Make depends a separate target. Now you can select when the dependency list is traversed.
1994-11-15 10:16:56 +00:00
${BUILD_COOKIE}:
@echo "===> Building for ${DISTNAME}"
Don't use build: ... pre-build, move pre-build inside BUILD_COOKIE instead
1994-12-17 01:58:11 +00:00
@${MAKE} ${.MAKEFLAGS} pre-build
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.if defined(USE_GMAKE)
Set PREFIX in the build target. Suggested by John Fieber.
1995-01-23 18:22:36 +00:00
@(cd ${WRKSRC}; ${GMAKE} PREFIX=${PREFIX} ${MAKE_FLAGS} ${MAKEFILE} ${ALL_TARGET})
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.else defined(USE_GMAKE)
Set PREFIX in the build target. Suggested by John Fieber.
1995-01-23 18:22:36 +00:00
@(cd ${WRKSRC}; ${MAKE} PREFIX=${PREFIX} ${MAKE_FLAGS} ${MAKEFILE} ${ALL_TARGET})
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.endif
added hook for post-build script Reviewed by: Submitted by:
1994-08-30 16:39:27 +00:00
@if [ -f ${SCRIPTDIR}/post-build ]; then \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
env CURDIR=${.CURDIR} DISTDIR=${DISTDIR} WRKDIR=${WRKDIR} \
WRKSRC=${WRKSRC} PATCHDIR=${PATCHDIR} SCRIPTDIR=${SCRIPTDIR} \
Whoops! Forgot to pass PREFIX to the configure subshells. Done.
1994-10-04 14:46:34 +00:00
FILESDIR=${FILESDIR} PORTSDIR=${PORTSDIR} PREFIX=${PREFIX} \
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
DEPENDS="${DEPENDS}" \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
sh ${SCRIPTDIR}/post-build; \
added hook for post-build script Reviewed by: Submitted by:
1994-08-30 16:39:27 +00:00
fi
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${BUILD_COOKIE}
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.endif
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
.if !target(pre-patch)
pre-patch:
@${DO_NADA}
.endif
.if !target(patch)
Sort out dependencies. Now they look like: patch: extract configure: depends patch build: configure install: build Does this look ok?
1995-01-05 08:15:53 +00:00
patch: extract ${PATCH_COOKIE}
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
${PATCH_COOKIE}:
patch: pre-patch ... is wrong, move pre-patch inside PATCH_COOKIE
1994-12-14 05:53:09 +00:00
@${MAKE} ${.MAKEFLAGS} pre-patch
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
.if defined(PATCH_DEBUG)
<Sigh> Got the placing of a .if wrong. Fix it.
1994-12-11 14:50:40 +00:00
@if [ -d ${PATCHDIR} ]; then \
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
echo "===> Applying patches for ${DISTNAME}" ; \
<Sigh> Got the placing of a .if wrong. Fix it.
1994-12-11 14:50:40 +00:00
for i in ${PATCHDIR}/patch-*; do \
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
echo "===> Applying patch $$i" ; \
<Sigh> Got the placing of a .if wrong. Fix it.
1994-12-11 14:50:40 +00:00
${PATCH} ${PATCH_ARGS} < $$i; \
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
done; \
fi
<Sigh> Got the placing of a .if wrong. Fix it.
1994-12-11 14:50:40 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${PATCH_COOKIE}
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
.else
<Sigh> Got the placing of a .if wrong. Fix it.
1994-12-11 14:50:40 +00:00
@if [ -d ${PATCHDIR} ]; then \
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
echo "===> Applying patches for ${DISTNAME}" ; \
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
for i in ${PATCHDIR}/patch-*; \
Last gremlin-killer of the day. Typo fixed and missing .endif replaced.
1994-12-11 15:31:22 +00:00
do ${PATCH} ${PATCH_ARGS} < $$i; \
1) Small tidyup 2) Change INSTALL_MANPAGES to NO_INSTALL_MANPAGES and document it 3) Add a PKGNAME variable to allow the package name not to be dictated by stupid DISTNAMEs 4) Add a PATCH_DEBUG option and a slight change to the default patch system - add --forward to help ensure correct patching
1994-12-10 18:07:38 +00:00
done;\
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
fi
@${TOUCH} ${TOUCH_FLAGS} ${PATCH_COOKIE}
.endif
Last gremlin-killer of the day. Typo fixed and missing .endif replaced.
1994-12-11 15:31:22 +00:00
.endif
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
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
1994-08-25 22:59:56 +00:00
.if !target(pre-configure)
pre-configure:
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
@${DO_NADA}
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
1994-08-25 22:59:56 +00:00
.endif
Some cosmetic changes. Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
1994-08-24 14:49:33 +00:00
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.if !target(configure)
Sort out dependencies. Now they look like: patch: extract configure: depends patch build: configure install: build Does this look ok?
1995-01-05 08:15:53 +00:00
configure: depends patch ${CONFIGURE_COOKIE}
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
${CONFIGURE_COOKIE}:
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
@echo "===> Configuring for ${DISTNAME}"
Add ${.MAKEFLAGS} to sub-makes, pointed by Rod
1994-10-14 21:58:09 +00:00
@${MAKE} ${.MAKEFLAGS} pre-configure
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
@if [ -f ${SCRIPTDIR}/pre-configure ]; then \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
env CURDIR=${.CURDIR} DISTDIR=${DISTDIR} WRKDIR=${WRKDIR} \
WRKSRC=${WRKSRC} PATCHDIR=${PATCHDIR} SCRIPTDIR=${SCRIPTDIR} \
Whoops! Forgot to pass PREFIX to the configure subshells. Done.
1994-10-04 14:46:34 +00:00
FILESDIR=${FILESDIR} PORTSDIR=${PORTSDIR} PREFIX=${PREFIX} \
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
DEPENDS="${DEPENDS}" \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
sh ${SCRIPTDIR}/pre-configure; \
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
fi
Whoops, the check for a missing distfile was slightly bogus. Now it works. Submitted by: jkh
1994-08-21 14:32:40 +00:00
@if [ -f ${SCRIPTDIR}/configure ]; then \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
env CURDIR=${.CURDIR} DISTDIR=${DISTDIR} WRKDIR=${WRKDIR} \
WRKSRC=${WRKSRC} PATCHDIR=${PATCHDIR} SCRIPTDIR=${SCRIPTDIR} \
Whoops! Forgot to pass PREFIX to the configure subshells. Done.
1994-10-04 14:46:34 +00:00
FILESDIR=${FILESDIR} PORTSDIR=${PORTSDIR} PREFIX=${PREFIX} \
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
DEPENDS="${DEPENDS}" \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
sh ${SCRIPTDIR}/configure; \
Whoops, the check for a missing distfile was slightly bogus. Now it works. Submitted by: jkh
1994-08-21 14:32:40 +00:00
fi
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
.if defined(HAS_CONFIGURE)
Preset ac_cv_path_CC="${CC}" before running ./configure, needed for Autoconf 2
1995-01-01 20:06:20 +00:00
@(cd ${WRKSRC}; CC="${CC}" ac_cv_path_CC="${CC}" CFLAGS="${CFLAGS}" \
Use absolute path for install passed to configure to disallow prepending ../ in second level Makefiles
1995-01-12 02:29:42 +00:00
INSTALL="/usr/bin/install -c -o ${BINOWN} -g ${BINGRP}" \
INSTALL_PROGRAM="/usr/bin/install ${COPY} ${STRIP} -o ${BINOWN} -g ${BINGRP} -m ${BINMODE}" \
Allow arbitrarily named configure script for use w/ HAS_CONFIGURE.
1995-02-06 08:52:19 +00:00
./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS})
Add a new flag: USE_IMAKE This will cause the configure pass to do an `xmkmf' if set. Submitted by: jkh
1994-08-25 13:53:02 +00:00
.endif
.if defined(USE_IMAKE)
If USE_GMAKE is defined, use ${GMAKE} in ${XMKMF} && ${MAKE} Makefiles
1994-11-16 23:14:22 +00:00
.if defined(USE_GMAKE)
@(cd ${WRKSRC}; ${XMKMF} && ${GMAKE} Makefiles)
.else
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
@(cd ${WRKSRC}; ${XMKMF} && ${MAKE} Makefiles)
If USE_GMAKE is defined, use ${GMAKE} in ${XMKMF} && ${MAKE} Makefiles
1994-11-16 23:14:22 +00:00
.endif
Start really adding some features here. Let's see: 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
1994-08-21 16:37:09 +00:00
.endif
@if [ -f ${SCRIPTDIR}/post-configure ]; then \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
env CURDIR=${.CURDIR} DISTDIR=${DISTDIR} WRKDIR=${WRKDIR} \
WRKSRC=${WRKSRC} PATCHDIR=${PATCHDIR} SCRIPTDIR=${SCRIPTDIR} \
Whoops! Forgot to pass PREFIX to the configure subshells. Done.
1994-10-04 14:46:34 +00:00
FILESDIR=${FILESDIR} PORTSDIR=${PORTSDIR} PREFIX=${PREFIX} \
Following changes from Robert Withrow (+ a few mods): 1. Make DEPENDS fully qualified, and not implictly assume relative to ${PORTSDIR}. This allows more arbitrary dependencies to be specified. This also means that DEPENDS= x11/foo needs to be changed to DEPENDS= ${PORTSDIR}/x11/foo in any Makefiles. I'll try to do these changes myself. 2. Add an option NO_DEPENDS to disable the automagic building of depended ports. Submitted by: rww
1994-10-05 22:28:45 +00:00
DEPENDS="${DEPENDS}" \
May the saints praise Robert Withrow <witr@rwwa.com> for showing me the light. `env' can be used to pass environment variables to shell scripts this way, which means that all *configure/post-build scripts _no longer take any arguments_; everything they should need (and more) is now available in the environment. I'm working now to adapt the older shell scripts over, but if you want beat me to it on some of your own ports, don't let me stop you! :) Submitted by: witr
1994-10-03 13:45:03 +00:00
sh ${SCRIPTDIR}/post-configure; \
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
fi
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${CONFIGURE_COOKIE}
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
.endif
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
.if !target(pre-fetch)
pre-fetch:
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
@${DO_NADA}
Some cosmetic changes. Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
1994-08-24 14:49:33 +00:00
.endif
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
.if !target(fetch)
fetch: pre-fetch
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
@if [ ! -d ${DISTDIR} ]; then mkdir -p ${DISTDIR}; fi
@(cd ${DISTDIR}; \
for file in ${DISTFILES}; do \
Make fetch a bit more forgiving of subdirs.
1995-01-30 10:06:56 +00:00
if [ ! -f $$file -a ! -f `basename $$file` ]; then \
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
echo ">> $$file doesn't seem to exist on this system."; \
Ok, I think I have this whole HOME_LOCATION / MASTER_SITE stuff resolved to a reasonable compromise: MASTER_SITES now contains a space seperated list of sites for which each DISTFILE may be retrieved. This should be a directory spec, which will be concatenated with each file in DISTFILES. HOME_LOCATION is *gone* now and isn't used for anything, so you can delete it from your Makefiles. If you want to force a fetch from a given location, simply do something like: MASTER_SITES= ftp://fnord.foo.bar/pub/dist DISTFILES= a.tar.gz b.tar.gz Your entry in MASTER_SITES will be tried first to fetch a.tar.gz and b.tar.gz, followed by any master sites we have set up (right now, only freebsd.cdrom.com).
1994-09-13 06:22:11 +00:00
echo ">> Attempting to fetch it from a master site."; \
for site in ${MASTER_SITES}; do \
Don't assume / seperator between site name and dist file in fetch.
1994-09-14 15:30:44 +00:00
if ${NCFTP} ${NCFTPFLAGS} $${site}$${file}; then \
Ok, I think I have this whole HOME_LOCATION / MASTER_SITE stuff resolved to a reasonable compromise: MASTER_SITES now contains a space seperated list of sites for which each DISTFILE may be retrieved. This should be a directory spec, which will be concatenated with each file in DISTFILES. HOME_LOCATION is *gone* now and isn't used for anything, so you can delete it from your Makefiles. If you want to force a fetch from a given location, simply do something like: MASTER_SITES= ftp://fnord.foo.bar/pub/dist DISTFILES= a.tar.gz b.tar.gz Your entry in MASTER_SITES will be tried first to fetch a.tar.gz and b.tar.gz, followed by any master sites we have set up (right now, only freebsd.cdrom.com).
1994-09-13 06:22:11 +00:00
break; \
fi \
Missing semi-colon after a done statement. Fixed.
1994-09-13 08:40:27 +00:00
done; \
Make fetch a bit more forgiving of subdirs.
1995-01-30 10:06:56 +00:00
if [ ! -f $$file -a ! -f `basename $$file` ]; then \
Ok, I think I have this whole HOME_LOCATION / MASTER_SITE stuff resolved to a reasonable compromise: MASTER_SITES now contains a space seperated list of sites for which each DISTFILE may be retrieved. This should be a directory spec, which will be concatenated with each file in DISTFILES. HOME_LOCATION is *gone* now and isn't used for anything, so you can delete it from your Makefiles. If you want to force a fetch from a given location, simply do something like: MASTER_SITES= ftp://fnord.foo.bar/pub/dist DISTFILES= a.tar.gz b.tar.gz Your entry in MASTER_SITES will be tried first to fetch a.tar.gz and b.tar.gz, followed by any master sites we have set up (right now, only freebsd.cdrom.com).
1994-09-13 06:22:11 +00:00
echo ">> Couldn't fetch it - please try to retreive this";\
echo ">> port manually into ${DISTDIR} and try again."; \
Here's my first cut at doing auto-fetch with ncftp. The extract rule is turning into the original make rule from hell! Submitted by: jkh
1994-09-01 18:03:37 +00:00
exit 1; \
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
fi; \
Here's my first cut at doing auto-fetch with ncftp. The extract rule is turning into the original make rule from hell! Submitted by: jkh
1994-09-01 18:03:37 +00:00
fi \
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
done)
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
.endif
Gary Palmer's patches for checksumming and description. Submitted by: gpalmer
1995-01-04 23:06:38 +00:00
.if !target(makesum)
makesum: fetch
Early md5-checksumming code. This seems to work fine on my machine but needs more testing on more ports than I have on my box.
1994-12-11 20:36:12 +00:00
@if [ ! -d ${FILESDIR} ]; then mkdir -p ${FILESDIR}; fi
@if [ -f ${MD5_FILE} ]; then rm -f ${MD5_FILE}; fi
@(cd ${DISTDIR}; \
for file in ${DISTFILES}; do \
${MD5} $$file >> ${MD5_FILE}; \
done)
.endif
Gary Palmer's patches for checksumming and description. Submitted by: gpalmer
1995-01-04 23:06:38 +00:00
.if !target(checksum)
checksum: fetch
Early md5-checksumming code. This seems to work fine on my machine but needs more testing on more ports than I have on my box.
1994-12-11 20:36:12 +00:00
@if [ ! -f ${MD5_FILE} ]; then \
echo ">> No MD5 checksum file."; \
Move pre-extract target inside COOKIE Add checksum check for extract, if checksum file present
1995-01-06 22:14:12 +00:00
else \
Oops. Fix up the checksum routine - my last commit broke it slightly.
1995-01-22 20:40:48 +00:00
(cd ${DISTDIR}; OK=""; \
for file in ${DISTFILES}; do \
CKSUM=`${MD5} $$file | awk '{print $$4}'`; \
CKSUM2=`grep "($$file)" ${MD5_FILE} | awk '{print $$4}'`; \
if [ "$$CKSUM2" = "" ]; then \
echo ">> No checksum recorded for $$file"; \
OK="false"; \
elif [ "$$CKSUM" != "$$CKSUM2" ]; then \
echo ">> Checksum mismatch for $$file"; \
Always go to ${WRKDIR} before extraction. Modify the tar extract command args to take advantage of this. Pointed-out-by: asami
1995-02-17 08:52:55 +00:00
exit 1; \
Oops. Fix up the checksum routine - my last commit broke it slightly.
1995-01-22 20:40:48 +00:00
fi; \
done; \
if [ "$$OK" = "" ]; then \
echo "Checksums OK."; \
else \
echo "Checksums OK for files that have them."; \
fi) ; \
Move pre-extract target inside COOKIE Add checksum check for extract, if checksum file present
1995-01-06 22:14:12 +00:00
fi
Early md5-checksumming code. This seems to work fine on my machine but needs more testing on more ports than I have on my box.
1994-12-11 20:36:12 +00:00
.endif
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
.if !target(pre-extract)
pre-extract:
@${DO_NADA}
.endif
.if !target(extract)
# We need to depend on .extract_done rather than the presence of ${WRKDIR}
# because if the user interrupts the extract in the middle (and it's often
# a long procedure), we get tricked into thinking that we've got a good dist
# in ${WRKDIR}.
Move pre-extract target inside COOKIE Add checksum check for extract, if checksum file present
1995-01-06 22:14:12 +00:00
extract: fetch ${EXTRACT_COOKIE}
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
${EXTRACT_COOKIE}:
Move pre-extract target inside COOKIE Add checksum check for extract, if checksum file present
1995-01-06 22:14:12 +00:00
@${MAKE} ${.MAKEFLAGS} checksum pre-extract
Rearrange this a bit while I think about the whole problem of fetching multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
1994-09-09 06:21:43 +00:00
@echo "===> Extracting for ${DISTNAME}"
@rm -rf ${WRKDIR}
@mkdir -p ${WRKDIR}
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
.if defined(EXTRACT_ONLY)
@for file in ${EXTRACT_ONLY}; do \
Always go to ${WRKDIR} before extraction. Modify the tar extract command args to take advantage of this. Pointed-out-by: asami
1995-02-17 08:52:55 +00:00
if ! (cd ${WRKDIR};${EXTRACT_CMD} ${EXTRACT_ARGS} ${DISTDIR}/$$file);\
then \
Catch case where extraction fails. Thanks!
1995-01-10 12:23:44 +00:00
exit 1; \
fi \
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
done
.else
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
@for file in ${DISTFILES}; do \
Always go to ${WRKDIR} before extraction. Modify the tar extract command args to take advantage of this. Pointed-out-by: asami
1995-02-17 08:52:55 +00:00
if ! (cd ${WRKDIR};${EXTRACT_CMD} ${EXTRACT_ARGS} ${DISTDIR}/$$file);\
then \
Catch case where extraction fails. Thanks!
1995-01-10 12:23:44 +00:00
exit 1; \
fi \
Annual simplification drive: 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
1994-09-10 22:26:47 +00:00
done
More fixes and general cleanup. Add more fine-grained control over what is fetched and what is actually unpacked.
1994-09-11 12:55:54 +00:00
.endif
2 changes: 1. Make build rely on a BUILD_COOKIE now. I'm tired of builds being redone gratuitously while I'm trying to debug a tree build problem. 2. Remove all the literal `touch -f' commands and indirect them through variables. This lets you "leave tracks" in different ways, depending on the medium. Just part 1 of my planned changes to make builds directly off the CD work.
1994-11-01 18:09:22 +00:00
@${TOUCH} ${TOUCH_FLAGS} ${EXTRACT_COOKIE}
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.endif
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
.if !target(pre-clean)
pre-clean:
@${DO_NADA}
.endif
Some cosmetic changes. Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
1994-08-24 14:49:33 +00:00
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.if !target(clean)
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
clean: pre-clean
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
@echo "===> Cleaning for ${DISTNAME}"
Add reinstall target for Poul-H. This lets you install again from the same build, ignoring the INSTALL_COOKIE.
1994-11-03 19:14:08 +00:00
@rm -f ${EXTRACT_COOKIE} ${CONFIGURE_COOKIE} ${INSTALL_COOKIE} \
Add patch cookies. This should prevent gratuitous patch re-application attempts.
1994-11-11 09:45:33 +00:00
${BUILD_COOKIE} ${PATCH_COOKIE}
Don't use a rm -rf WORKDIR if NO_WRKDIR is defined. You have a good chance to blow away your current dir, because WRKDIR == CURDIR. This should help tcpblast to not blow away itself in the clean target :-).
1994-11-21 10:30:37 +00:00
.if !defined(NO_WRKDIR)
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
@rm -rf ${WRKDIR}
.endif
Don't use a rm -rf WORKDIR if NO_WRKDIR is defined. You have a good chance to blow away your current dir, because WRKDIR == CURDIR. This should help tcpblast to not blow away itself in the clean target :-).
1994-11-21 10:30:37 +00:00
.endif
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
Lots of changes - get the NO_XXX things over, add @'s to the touches for default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
1994-08-28 14:41:34 +00:00
# No pre-targets for depend or tags. It would be silly.
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
# Depend is generally meaningless for arbitrary ports, but if someone wants
# one they can override this. This is just to catch people who've gotten into
# the habit of typing `make depend all install' as a matter of course.
#
.if !target(depend)
depend:
Commit my new ports make macros. Still not 100% complete yet by any means but fairly usable at this stage. Submitted by: jkh
1994-08-21 13:12:57 +00:00
.endif
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
# Same goes for tags
.if !target(tags)
tags:
.endif
Reference in New Issue Copy Permalink