mkdep(1) [freebsd man page]

MKDEP(1)						    BSD General Commands Manual 						  MKDEP(1)

NAME

     mkdep -- construct Makefile dependency list

SYNOPSIS

     mkdep [-ap] [-f file] [flags] file ...

DESCRIPTION

     The mkdep utility takes a set of flags for the C compiler and a list of C source files as arguments and constructs a set of include file
     dependencies which are written into the file ``.depend''.	An example of its use in a Makefile might be:

	   CFLAGS= -O -I../include
	   SRCS= file1.c file2.c

	   depend:
		   mkdep ${CFLAGS} ${SRCS}

     where the macro SRCS is the list of C source files and the macro CFLAGS is the list of flags for the C compiler.

     The user has the ability to change the preprocessor and preprocessor options used.  For instance, to use gcc as the preprocessor and to
     ignore system headers, one would use

	   depend:
		   env MKDEP_CPP="gcc -E" MKDEP_CPP_OPTS=-MM mkdep 
			   ${CFLAGS} ${SRCS}

     The options are as follows:

     -a      Append to the output file, so that multiple mkdep's may be run from a single Makefile.

     -f      Write the include file dependencies to file, instead of the default ``.depend''.

     -p      Cause mkdep to produce dependencies of the form:

		   program: program.c

	     so that subsequent makes will produce program directly from its C module rather than using an intermediate .o module.  This is useful
	     for programs whose source is contained in a single module.

ENVIRONMENT

     CC 	     Specifies the C compiler to use.  The specified compiler is expected to have options consistent with the GNU C compiler.

     MKDEP_CPP	     Specifies the preprocessor to use.  The default is "${CC} -E".

     MKDEP_CPP_OPTS  Specifies the non-CFLAGS options for the preprocessor.  The default is "-M".

FILES

     .depend  File containing list of dependencies.

SEE ALSO

     cc(1), cpp(1), make(1)

HISTORY

     The mkdep command appeared in 4.3BSD-Tahoe.

BSD
								   June 6, 1993 							       BSD

MKDEP(1)						    BSD General Commands Manual 						  MKDEP(1)

NAME

     mkdep -- construct Makefile dependency list

SYNOPSIS

     mkdep [-aDdopq] [-f file] [-s suffixes] -- [flags] file ...

DESCRIPTION

     mkdep takes a set of flags for the C compiler and a list of C source files as arguments and constructs a set of include file dependencies
     which are written into the file ``.depend''.  An example of its use in a Makefile might be:

	   CFLAGS= -O -I../include
	   SRCS= file1.c file2.c

	   depend:
		   mkdep -- ${CFLAGS} ${SRCS}

     where the macro SRCS is the list of C source files and the macro CFLAGS is the list of flags for the C compiler.

     The options are as follows:

     -a      Append to the output file, so that multiple mkdep's may be run from a single Makefile.

     -D      Post process (as -d) but read the list of filenames from stdin.

     -d      Post process and merge previously created (for example by ``cc -MD x.c'') depend files into a single file.

     -f      Write the include file dependencies to file, instead of the default ``.depend''.

     -o      Add an additional .OPTIONAL line for each dependent file.

     -p      Cause mkdep to produce dependencies of the form:

		   program: program.c

	     so that subsequent makes will produce program directly from its C module rather than using an intermediate .o module.  This is useful
	     for programs whose source is contained in a single module.  -p is equivalent to specifying a null suffix with -s.

     -q      Do not print a warning for inaccessible files when -d is given.

     -s      Expand each target filename to a list, replacing the '.o' suffix with each element of suffixes.  The list of suffixes may be space or
	     comma separated.

FILES

     .depend  File containing list of dependencies.

SEE ALSO

     cc(1), cpp(1), make(1)

HISTORY

     The mkdep command appeared in 4.3BSD-Tahoe.

BUGS

     Some characters special to make(1), most notably the comment character, are not escaped correctly if they appear in file names.  This can
     lead to unparseable output or silently cause dependencies to be lost.

BSD
								 October 15, 2010							       BSD