GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
MKIFY(1) FreeBSD General Commands Manual MKIFY(1)

mkify
BSDBuild auto-bundling script

mkify module ...

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(5) 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(1) 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.

mkconfigure(1), build.common.mk(5), build.lib.mk(5), build.prog.mk(5)

http://hypertriton.com/bsdbuild/

July 19, 2007 FreeBSD 13.1-RELEASE

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.