module ...
DESCRIPTION
The mkify utility copies installed BSDBuild include files from their system location to mk under the working directory. It accepts a list of BSDBuild modules as arguments (e.g., prog will cause build.prog.mk to be installed). mkify also scans for include directives and will automatically install all dependencies as well.

The BSDBuild build system is designed to be bundled with applications as a stand-alone set of make include files, which are typically installed in a directory named mk in the top-level directory (or some other central location) in an application source code, such that people building applications which use the BSDBuild build system do not need to have BSDBuild or any other software installed on their systems.

While the need for a mk directory may be perceived as a problem, there are several advantages:
  1. Makefiles are not generated, they can be edited directly. BSDBuild will generate Makefiles only when performing concurrent builds (i.e., building object files in a directory separate from the source tree).
  2. BSDBuild makefiles are orders of magnitude smaller than any generated Makefile, avoiding masses of redundant code.
  3. There is no Makefile.in, so the total number of files in your tree is reduced.

SEE ALSO
mkconfigure, build.common.mk, build.lib.mk, build.prog.mk

http://hypertriton.com/bsdbuild/

(c) 2016 Hypertriton Inc.
Hosted on OpenBSD servers at Csoft.net in NYC.
Sponsored by ElectronTubeStore.com.
Hosted by Csoft.net Sponsored by ElectronTubeStore.com