-
Notifications
You must be signed in to change notification settings - Fork 118
/
Makefile.template
276 lines (239 loc) · 8.86 KB
/
Makefile.template
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
# 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 of port if using lang/python module
#
#MODPY_EGG_VERSION = ???
# 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
# 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)
#
# If port is a Python module (py-*) that is or might be used by other Python
# ports, set FLAVOR=python3 and FLAVORS=python3
#
# 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>