123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263 |
- .\" $XConsortium: xmkmf.man,v 1.3 91/08/17 13:06:59 rws Exp $
- .TH XMKMF 1 "Release 5" "X Version 11"
- .SH NAME
- xmkmf \- create a Makefile from an Imakefile
- .SH SYNOPSIS
- .B xmkmf
- [ -a ] [
- .I topdir
- [
- .I curdir
- ] ]
- .SH DESCRIPTION
- The
- .I xmkmf
- command is the normal way to create a
- .I Makefile
- from an
- .I Imakefile
- shipped with third-party software.
- .PP
- When invoked with no arguments in a directory containing an
- .I Imakefile,
- the
- .I imake
- program is run with arguments appropriate for your system
- (configured into
- .I xmkmf
- when X was built) and generates a
- .I Makefile.
- .PP
- When invoked with the
- .I \-a
- option,
- .I xmkmf
- builds the
- .I Makefile
- in the current directory, and then automatically executes
- ``make Makefiles'' (in case there are subdirectories),
- ``make includes'',
- and ``make depend'' for you.
- This is the normal way to configure software that is outside
- the MIT X build tree.
- .PP
- If working inside the MIT X build tree (unlikely unless you are an X
- developer, and even then this option is never really used), the
- .I topdir
- argument should be specified as the relative pathname from the
- current directory to the top of the build tree. Optionally,
- .I curdir
- may be specified as a relative pathname from the top of the build
- tree to the current directory. It is necessary to supply
- .I curdir
- if the current directory has subdirectories, or the
- .I Makefile
- will not be able to build the subdirectories.
- If a
- .I topdir
- is given,
- .I xmkmf
- assumes nothing is installed on your system and looks for files in
- the build tree instead of using the installed versions.
- .SH "SEE ALSO"
- imake(1)
|