ports/infrastructure/templates/Makefile.template

# Replace ??? with appropriate values
# Remove extraneous comments before commit
# Use /usr/ports/infrastructure/bin/portcheck

# Reasons why the port/package shouldn't be built
#
#ONLY_FOR_ARCHS =	???
#NOT_FOR_ARCHS =	???
#COMES_WITH =		???
#BROKEN =		reason

#
# Very short description of the package (<=60 chars, usually starts lower-case)
#		|----------------------------------------------------------|
COMMENT =	???
# COMMENT-foo =	???	for multi packages

#
# Version number used in Python dist-info/egg-info files if using
# lang/python module; often the upstream release version number,
# but not always. Check pkg/PLIST after generating and adjust if
# necessary.
#
#MODPY_DISTV =	???

# MODGO_MODNAME should be set to the 'module' specified in the 'go.mod' file.
#MODGO_MODNAME =	github.com/test/app
#
# Version of port if using lang/go and MODGO_MODULES
#
#MODGO_VERSION =	0.1.1

# What port/package will be created
#
# DISTNAME should not include suffix (like .tar.gz .tgz .tar.bz2 etc.)
DISTNAME =	???
# PKGNAME defaults to DISTNAME unless changed
#PKGNAME =	???
#PKGNAME-foo =	???	for multi packages

#
# On source code hosting platforms use static tarballs over generated ones.
# It's easy to distinguish between them on github, gitlab and codeberg by
# looking at the file URL:
# /releases/ -> preferred. Use SITES and DISTNAME.
# /archive/ -> use DIST_TUPLE (use only if there is no release version).
#
# platform: codeberg, github, gitlab, kde, srht, gnome, fdo
# account: usually the account or organisation name
# project: the project or repository name
# id: either a tag name or commit hash.
#   Tag names with standard tag formats, like 1.0.1 or v1.0, set an
#   appropriate PKGNAME automatically. Otherwise, set it yourself.
#   "make show=PKGNAMES" will help identify if that's needed.
#   For a commit hash, use the full hash (not shortened), and set PKGNAME.
# subdir: usually ".", otherwise the extracted files are moved to another
#   directory under WRKDIST. Mostly useful for git submodules.
#DIST_TUPLE +=	platform account project id subdir

# for any port that creates shared libraries.
# both libtool and cmake automatically set filenames based on this variable.
# for libtool- or cmake-based ports, have a look at WRKBUILD/shared_libs.log
#SHARED_LIBS =	???	0.0

# the category used in the directory name, /usr/ports/<category>/portname,
# must be included and listed first.
CATEGORIES =	???

# https preferred for HOMEPAGE
#HOMEPAGE =	???	URL

# person who is responsible for the port. Use a complete email address with
# a real name, e.g., "MAINTAINER = John Doe <doe57@machine.somewhere.org>".
# If you maintain several ports, use the same line each time.
# If you no longer use the port, or are unwilling/unable to handle issues
# in a timely manner, *leave the field blank*.
# Default value is ports@openbsd.org, no need to fill in
#MAINTAINER =		???

# Licensing:  This determines what we can distribute through ftp.
# When you determine the license type, make sure to look at ALL distfiles.
# Every distfile can have a different license.  The PERMIT_* values are
# determined by the most restrictive license.  If you have two licenses
# that are in conflict, set PERMIT_* based on the most restrictive one.
# Make SURE you get these values right.

# Put a comment there to state what's going on.
# Can be as brief as `BSD' or `GPLv2+', but it'd better be easy to check,
# if someone wants to double-check licensing.
# For GPL, the applicable versions must be included (e.g. v2+, v2 only, v3+).
# If both PERMIT_* are Yes, just setting 'PERMIT_PACKAGE=Yes' is enough.
#PERMIT_PACKAGE =	Yes | Reason if No
#PERMIT_DISTFILES =	Yes | Reason if No

# If pledge is used, annotate with `uses pledge()' in a comment

# "make port-lib-depends-check" can help
#WANTLIB =		???

# where the source files and patches can be fetched
#
SITES =		???
#SITES =		${SITE_SOURCEFORGE:=subdir/}
#SITES =		${SITE_foo:=subdir/}

# if more master sites are needed...
#SITES.sufx =
# ...
#DISTFILES =		???

# for grabbing DISTFILES from SITES.sufx
#DISTFILES.sufx = ...
#EXTRACT_ONLY =		???

# Needs to be specified if tarball does not end with .tar.gz
#EXTRACT_SUFX =		.tar.bz2

# Fix dos line-endings in files needing patches
#FIX_CRLF_FILES =	???

# Optional subdirectory of DISTDIR where distfiles and patches will be placed
#DIST_SUBDIR =		???

# use PATCHFILES.sufx for going to SITES.sufx
#PATCHFILES =		???
#PATCH_DIST_STRIP =	-p0

# Standard for C++ ports:
#COMPILER =		base-clang ports-gcc base-gcc
# Standard for C++11 or newer:
#COMPILER =		base-clang ports-gcc
# Ports that require a non-default compiler that do *not* use C++ should set this:
#COMPILER_LANGS =	c

# Any modules we may be using
#MODULES =		???

#
# MODPY_ settings for when using lang/python module
#
# Get source from pypi.org
#MODPY_PI =		Yes
#MODPY_PYBUILD =	setuptools
#			or flit_core, hatchling, etc - see python-module(5)

#
# MODGO_ settings for when using lang/go module
#
# Get source from proxy.golang.org
#MODGO_MODULES =	modulename version
# These are needed for dependency resolution. We don't actually need the
# corresponding code.
#MODGO_MODFILES =	modulename version

# Dependencies
#BUILD_DEPENDS =	???
#RUN_DEPENDS =		???
#LIB_DEPENDS =		???
#TEST_DEPENDS =		???

#MAKE_FLAGS =		???
#MAKE_ENV =		???
#FAKE_FLAGS =		???
#TEST_FLAGS =		???

# build/configuration variables
#
#SEPARATE_BUILD =	Yes (build in a directory other than WRKSRC)
#USE_GMAKE =		Yes
#USE_GROFF =		Yes
# Programs that require GNU libtool to build instead of the OpenBSD one
# should use this option. Add a comment explaining why. Don't use this if
# a port requires libtool's .m4 files but otherwise can use OpenBSD libtool,
# in that case use "BUILD_DEPENDS=devel/libtool" instead.
#USE_LIBTOOL=		gnu
# Set CONFIGURE_STYLE to value corresponding to some standard configuration
#	  perl [modbuild]: perl's MakeMaker Makefile.PL (modbuild: perl's
#	  Module::Build Build.PL)
#	  gnu [autoconf] [old] [dest]: gnu style configure (old: no
#	  sysconfdir), (dest: add DESTDIR, does not handle it),
#	  autoconf: run autoconf to regenerate configure script. implies gnu.
#	  autoreconf: run autoreconf (or other script passed in AUTORECONF) to
#	   generate configure. implies gnu. adds dependencies automatically.
#	XXX: cygnus products do NOT use autoconf for making the main
#		configure from configure.in
#	  imake [noman]: port uses imake for configuration.
#	  (noman: no man page installation)
#	  simple: port has its own configure script
#	  none: override default CONFIGURE_STYLE coming from a module
#	        (needed for some ports using lang/python, etc.)
#CONFIGURE_STYLE =	
#CONFIGURE_SCRIPT =	??? (if other than configure)
#CONFIGURE_ARGS =	???
#CONFIGURE_ENV =	???

# if debug packages are a good idea, extra configure args may be necessary
# and DEBUG_PACKAGES will commonly be set to ${BUILD_PACKAGES}
#DEBUG_CONFIGURE_ARGS =	???
#DEBUG_PACKAGES = ${BUILD_PACKAGES}

# for gnu stuff
#AUTOCONF_VERSION =	??? (defaults to 2.13)
#AUTOMAKE_VERSION =	??? (defaults to 1.4)
# config.guess and others are copied here
#MODGNU_CONFIG_GUESS_DIRS = ??? (defaults to ${WRKSRC})

# common examples:
# - port has ready-generated autoconf configure script that can be used as-is:
#CONFIGURE_STYLE =	gnu
# - ready-generated script needs patching: preferably patch the input files
#   (configure.in, configure.ac, *.m4) rather than the generated script, this
#   is less likely to break during updates) - prefer to use the same version
#   of autoconf as was used upstream:
#CONFIGURE_STYLE =	gnu
#AUTOCONF_VERSION =	2.71
# - either no generated script was included (common with projects using git
#   archives), or both autoconf and automake input files need patching:
#CONFIGURE_STYLE =	autoreconf
#AUTOCONF_VERSION =	2.71
#AUTOMAKE_VERSION =	1.16
#AUTORECONF =		./autogen.sh (optional; "autoreconf --force --install"
#					is used by default)

# Is the build automagic or is it interactive
#
#IS_INTERACTIVE =		Yes
#TEST_IS_INTERACTIVE =		Yes

# Assume you have one multiple choice flavor: 1 2 3 and switches a b.
# You would write
#
#FLAVORS =	1 2 3 a b
#FLAVOR ?=
# grab multiple choice value
#CHOICE = ${FLAVOR:Na:Nb}
# check that CHOICE is 1 OR 2 OR 3, or error out
#.if ${CHOICE} == "1"
# code for 1
#.elif ${CHOICE} == "2"
# code for 2
#.elif ${CHOICE} == "3"
# code for 3
#.else
#ERRORS += "Fatal: Conflicting flavor: ${FLAVOR}"
#.endif
# check for switches
#.if ${FLAVOR:Ma}
# code for a
#.endif
#.if ${FLAVOR:Mb}
# code for b
#.endif

# Things that we don't want to do for this port/package
# Generally, DON'T set anything to No if it's not needed.
# The time gained is not worth it.
#
#NO_BUILD =		Yes
#NO_TEST =		Yes

# Overrides for default values
#
#CFLAGS =		???
#LDFLAGS =		???
#MAKE_FILE =		???
#PKG_ARCH =		??? (* for arch-independent packages)
#WRKDIST =		??? if other than ${WRKDIR}/${DISTNAME}
#WRKSRC =		??? if other than ${WRKDIST}
#WRKBUILD =		??? if other than ${WRKSRC}
#WRKCONF =		??? if other than ${WRKBUILD}

#ALL_TARGET =		???
#INSTALL_TARGET =	???
#TEST_TARGET =		???

.include <bsd.port.mk>