1 # @(#)bsd.README 8.2 (Berkeley) 4/2/94
2 # $FreeBSD: src/share/mk/bsd.README,v 1.25 2003/05/17 18:03:05 trhodes Exp $
4 This is the README file for the "include" files for the DragonFly
5 source tree. The files are installed in /usr/share/mk, and are, by
6 convention, named with the suffix ".mk". These files store several
7 build options and should be handled with caution.
9 Note, this file is not intended to replace reading through the .mk
10 files for anything tricky.
12 There are two main types of make include files. One type is the generally
13 usable make include files, such as bsd.prog.mk and bsd.lib.mk. The other is
14 the internal make include files, such as bsd.files.mk and bsd.man.mk, which
15 can not/should not be used directly but are used by the other make include
16 files. In most cases it is only interesting to include bsd.prog.mk or
19 bsd.cpu.custom.mk - handle CPU flags for custom compilers
20 bsd.cpu.gcc47.mk - handle GCC 4.7 specific CPU flags & variables
21 bsd.cpu.gcc50.mk - handle GCC 5.0 specific CPU flags & variables
22 bsd.cpu.gcc80.mk - handle GCC 8.0 specific CPU flags & variables
23 bsd.cpu.mk - handle CPU flags & variables
24 bsd.crunchgen.mk - building crunched binaries using crunchgen(1)
25 bsd.dep.mk - handle Makefile dependencies
26 bsd.doc.mk - building troff system documents
27 bsd.files.mk - install of general purpose files
30 bsd.incs.mk - install of include files
31 bsd.init.mk - initialization for the make include files
32 bsd.kmod.mk - building loadable kernel modules
33 bsd.lib.mk - support for building libraries
34 bsd.libnames.mk - define library names
35 bsd.links.mk - install of links (sym/hard)
36 bsd.man.mk - install of manual pages and their links
37 bsd.nls.mk - build and install of NLS catalogs
38 bsd.obj.mk - creating 'obj' directories and cleaning up
39 bsd.own.mk - define common variables
41 bsd.prog.mk - building programs from source files
42 bsd.subdir.mk - targets for building subdirectories
43 bsd.sys.mk - common settings used for building DragonFly sources
44 sys.mk - default rules for all makes
47 See also make(1), mkdep(1) and `PMake - A Tutorial',
48 located in /usr/src/share/doc/psd/12.make.
50 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
52 Random things worth knowing about this document:
54 If appropriate when documenting the variables the default value is
55 indicated using square brackets e.g. [gzip].
56 In some cases the default value depend on other values (e.g. system
57 architecture). In these cases the most common value is indicated.
59 This document contains some simple examples of the usage of the BSD make
60 include files. For more examples look at the makefiles in the DragonFly
63 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
65 RANDOM THINGS WORTH KNOWING:
67 The files are like C-style #include files, and pretty much behave like
68 you'd expect. The syntax is slightly different in that a single '.' is
69 used instead of the hash mark, i.e. ".include <bsd.prog.mk>".
71 One difference that will save you lots of debugging time is that inclusion
72 of the file is normally done at the *end* of the Makefile. The reason for
73 this is because .mk files often modify variables and behavior based on the
74 values of variables set in the Makefile. To make this work, remember that
75 the FIRST target found is the target that is used, i.e. if the Makefile has:
82 the command "make a" will echo "a". To make things confusing, the SECOND
83 variable assignment is the overriding one, i.e. if the Makefile has:
91 the command "make b" will echo "bar". This is for compatibility with the
92 way the V7 make behaved.
94 It's fairly difficult to make the BSD .mk files work when you're building
95 multiple programs in a single directory. It's a lot easier split up the
96 programs than to deal with the problem. Most of the agony comes from making
97 the "obj" directory stuff work right, not because we switch to a new version
98 of make. So, don't get mad at us, figure out a better way to handle multiple
99 architectures so we can quit using the symbolic link stuff. (Imake doesn't
102 The file .depend in the source directory is expected to contain dependencies
103 for the source files. This file is read automatically by make after reading
106 The variable DESTDIR works as before. It's not set anywhere but will change
107 the tree where the file gets installed.
109 The profiled libraries are no longer built in a different directory than
110 the regular libraries. A new suffix, ".po", is used to denote a profiled
113 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
115 The include file <sys.mk> has the default rules for all makes, in the BSD
116 environment or otherwise. You probably don't want to touch this file.
118 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
120 The include file <bsd.man.mk> handles installing manual pages and their
123 It has three targets:
128 install the manual pages and their links.
130 verify the validity of manual pages.
132 It sets/uses the following variables:
134 MANDIR Base path for manual installation.
142 MANSUBDIR Subdirectory under the manual page section, i.e. "/vax"
143 or "/tahoe" for machine specific manual pages.
145 MAN The manual pages to be installed (use a .1 - .9 suffix).
147 MANINSTALLFLAGS Additional flags to pass to install(1).
149 MLINKS List of manual page links (using a .1 - .9 suffix). The
150 linked-to file must come first, the linked file second,
151 and there may be multiple pairs. The files are soft-linked.
153 The include file <bsd.man.mk> includes a file named "../Makefile.inc" if
156 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
158 The include file <bsd.own.mk> contains the owners, groups, etc. for both
159 manual pages and binaries.
163 It sets/uses the following variables:
171 STRIP The flag passed to the install program to cause the binary
172 to be stripped. This is to be used when building your
173 own install script so that the entire system can be made
174 stripped/not-stripped using a single knob.
176 MANDIR Base path for manual installation.
184 This file is generally useful when building your own Makefiles so that
185 they use the same default owners etc. as the rest of the tree.
187 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
189 The include file <bsd.prog.mk> handles building programs from one or
190 more source files, along with their manual pages. It has a limited number
191 of suffixes, consistent with the current needs of the BSD tree.
193 It has seven targets:
196 build the program and its manual page
198 remove the program and any object files.
200 remove all of the files removed by the target clean, as
201 well as .depend, tags, and any manual pages.
203 make the dependencies for the source files, and store
204 them in the file .depend.
206 install the program and its manual pages; if the Makefile
207 does not itself define the target install, the targets
208 beforeinstall and afterinstall may also be used to cause
209 actions immediately before and after the install target
212 run lint on the source files
214 create a tags file for the source files.
216 It sets/uses the following variables:
224 CLEANFILES Additional files to remove and
225 CLEANDIRS additional directories to remove during clean and cleandir
226 targets. "rm -f" and "rm -rf" used respectively.
228 COPTS Additional flags to the compiler when creating C objects.
230 FILES A list of non-executable files.
231 The installation is controlled by the FILESNAME, FILESOWN,
232 FILESGRP, FILESMODE, FILESDIR variables that can be
233 further specialized by <VAR>_<file>.
235 LDADD Additional loader objects. Usually used for libraries.
236 For example, to load with the compatibility and utility
239 LDFILES=-lutil -lcompat
241 LDFLAGS Additional loader flags.
243 LINKS The list of binary links; should be full pathnames, the
244 linked-to file coming first, followed by the linked
245 file. The files are hard-linked. For example, to link
246 /bin/test and /bin/[, use:
248 LINKS= ${DESTDIR}/bin/test ${DESTDIR}/bin/[
250 MAN Manual pages (should end in .1 - .9). If no MAN variable
251 is defined, "MAN=${PROG}.1" is assumed.
253 PROG The name of the program to build. If not supplied, nothing
256 PROG_CXX If defined, the name of the program to build. Also
257 causes <bsd.prog.mk> to link the program with the
258 standard C++ library. PROG_CXX overrides the value
259 of PROG if PROG is also set.
261 PROGNAME The name that the above program will be installed as, if
262 different from ${PROG}.
264 SRCS List of source files to build the program. If SRCS is not
265 defined, it's assumed to be ${PROG}.c or, if PROG_CXX is
266 defined, ${PROG_CXX}.cc.
268 DPADD Additional dependencies for the program. Usually used for
269 libraries. For example, to depend on the compatibility and
270 utility libraries use:
272 DPADD= ${LIBCOMPAT} ${LIBUTIL}
274 There is a predefined identifier for each (non-profiled,
275 non-shared) library and object. Library file names are
276 transformed to identifiers by removing the extension and
277 converting to upper case.
279 There are no special identifiers for profiled or shared
280 libraries or objects. The identifiers for the standard
281 libraries are used in DPADD. This works correctly iff all
282 the libraries are built at the same time. Unfortunately,
283 it causes unnecessary relinks to shared libraries when
284 only the static libraries have changed. Dependencies on
285 shared libraries should be only on the library version
288 STRIP The flag passed to the install program to cause the binary
289 to be stripped. This is to be used when building your
290 own install script so that the entire system can be made
291 stripped/not-stripped using a single knob.
293 SUBDIR A list of subdirectories that should be built as well.
294 Each of the targets will execute the same target in the
297 SCRIPTS A list of interpreter scripts [file.{sh,csh,pl,awk,...}].
298 The installation is controlled by the SCRIPTSNAME, SCRIPTSOWN,
299 SCRIPTSGRP, SCRIPTSMODE, SCRIPTSDIR variables that can be
300 further specialized by SCRIPTS<VAR>_<script>.
302 The include file <bsd.prog.mk> includes the file named "../Makefile.inc"
303 if it exists, as well as the include file <bsd.man.mk>.
305 Some simple examples:
307 To build foo from foo.c with a manual page foo.1, use:
311 .include <bsd.prog.mk>
313 To build foo from foo.c with a manual page foo.2, add the line:
317 If foo does not have a manual page at all, add the line:
321 If foo has multiple source files, add the line:
323 SRCS= a.c b.c c.c d.c
325 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
327 The include file <bsd.subdir.mk> contains the default targets for building
328 subdirectories. It has the same seven targets as <bsd.prog.mk>: all, clean,
329 cleandir, depend, install, lint, and tags. For all of the directories
330 listed in the variable SUBDIRS, the specified directory will be visited
331 and the target made. There is also a default target which allows the
332 command "make subdir" where subdir is any directory listed in the variable
335 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
337 The include file <bsd.lib.mk> has support for building libraries. It has
338 the same seven targets as <bsd.prog.mk>: all, clean, cleandir, depend,
339 install, lint, and tags. It has a limited number of suffixes, consistent
340 with the current needs of the BSD tree.
342 It sets/uses the following variables:
344 LIBDIR Target directory for libraries.
346 LINTLIBDIR Target directory for lint libraries.
348 LIBGRP Library group.
350 LIBOWN Library owner.
352 LIBMODE Library mode.
354 LDADD Additional loader objects.
356 MAN The manual pages to be installed (use a .1 - .9 suffix).
358 SRCS List of source files to build the library. Suffix types
359 .s, .c, and .f are supported. Note, .s files are preferred
360 to .c files of the same name. (This is not the default for
363 The include file <bsd.lib.mk> includes the file named "../Makefile.inc"
364 if it exists, as well as the include file <bsd.man.mk>.
366 It has rules for building profiled objects; profiled libraries are
369 Libraries are ranlib'd before installation.