BUILD.PROG.MK(5)

✨ BUILD.PROG.MK(5) ✨

okay so bestie, welcome to build.prog.mk — the bsdbuild module, and it's literally the one that compiles executables for you 💅 (this is the build.prog.mk(5) page, File Formats Manual, in case you were wondering 🎀)

---

🌸 SYNOPSIS 🌸

.include <bsd.prog.mk>

that's it. that's the whole vibe. one line and you're in 🫶

---

💖 DESCRIPTION 💖

So the build.prog.mk module is what you use to compile an executable program out of a bunch of source files. Iconic. And it comes with built-in support for sources in all of these languages, no cap:

• C (*.c)
• C++ (*.cc or *.cpp)
• Objective C (*.m)
• Assembler (*.asm)
• Lex (*.l)
• Yacc (*.y)

like it just knows. main character energy tbh 👑

---

🔥 TARGETS 🔥

• ${PROG} — compiles/links the ${PROG} executable from the source files you specified. the whole point, honestly.
• ${GMONOUT} — compiles/links a profiled version of ${PROG}. fancy.
• clean-prog — cleans up the object files and executable files. self care ✨
• cleandir-prog — cleans up for packaging.
• install-prog — installs the program into the target installation directory (peep csoft.common.mk(5) for that one).
• deinstall-prog — uninstalls the program from the installation directory. we love a reversible decision 💀

---

🦋 VARIABLES 🦋

• PROG — filename of the target executable. heads up: platform-specific transforms may get applied to the name, so it might not come out exactly as you typed it 👀
• PROG_TYPE — the type of application. set it to ‘CLI’ for a command-line utility, ‘GUI’ for a graphical interface, or ‘DAEMON’ for a server program. defaults to ‘CLI’. what this setting actually means is platform-specific — and on the Windows platform, it tells the compiler to pick the appropriate PE header subsystem 🪟
• BINDIR — target installation directory for executables (usually set by configure).
• PROG_INSTALL — if you set it to ‘Yes’, the install target will install the program, otherwise it's a no-op. defaults to ‘Yes’.
• PROG_GUID — a Global Unique Identifier (GUID) for the program. exact interpretation is platform-specific 🤷
• GMONOUT — output filename for the profiled version of the program.
• CC — compiler for C, C++ and Objective C sources. defaults to ‘cc’.
• CFLAGS — compiler flags for C sources. defaults to ‘-O2 -g’.
• CXXFLAGS — compiler flags for C++ sources. defaults to ‘’ (yes, empty, it's giving minimalism).
• OBJCFLAGS — compiler flags for Objective C sources. defaults to ‘${CFLAGS}’.
• CPPFLAGS — compiler preprocessor flags, for sources in all languages that feature a C preprocessor.
• ASM — compiler for assembler sources. defaults to ‘nasm’.
• ASMFLAGS — compiler flags for assembler. defaults to ‘-g -w-orphan-labels’.
• LEX — path to the lex(1) lexical analyzer generator.
• YACC — path to the yacc(1) parser generator.
• LFLAGS — options for lex(1), defaults to ‘’.
• YFLAGS — options for yacc(1), defaults to ‘-d’.
• LIBL — libraries to use for Lex lexers. defaults to ‘-ll’.
• WINDRES — (specific to the win32 platform) path to the windres(1) utility, which generates windows resource files.
• WINRES — (specific to the win32 platform) resource file to use with windres(1).
• DATAFILES — list of data files to install into ${DATADIR}. important: these files must have been generated from the build process — meaning if you're using a separate build with --srcdir, the files you specify must exist in the build directory. don't come for me, that's just how it is 😭
• DATAFILES_SRC — files to install into ${DATADIR}. handled similarly to DATAFILES, except these specified files must exist in the source directory. see the difference? iconic.
• CONFDIR — system-wide configuration files get installed into this directory. it's usually set relative to ‘${SYSCONFDIR}’, for example ‘${SYSCONFDIR}/MyApplication’.
• CONF — list of configuration files to install into ${CONFDIR}. but bestie, listen — the install target will not override existing configuration files. instead it prints a “The following configuration files have been preserved” message. respectful king behavior honestly 🫶
• CONF_OVERWRITE — overwrite any existing configuration file on installation. default is "No".

⚠️ note the difference between DATAFILES (lives in the build directory) and DATAFILES_SRC (lives in the source directory) — mixing them up is a whole mood killer.

---

🌈 SEE ALSO 🌈

• build.common.mk(5)
• build.lib.mk(5)

---

💜 HISTORY 💜

build.prog.mk first appeared in BSDBuild 1.0 ✨

BSDBuild is based on the 4.4BSD build system. heritage! legacy! we stan 👑

---

that's the whole page bestie, go compile something cute 🎀💖

Debian · July 18, 2007 · BUILD.PROG.MK(5) — mwah, that's the source and the date, signin' off 💅✨