Lines Matching refs:code

58 to avoid trouble on systems where the @code{SHELL} variable might be
60 @code{make}.)
62 Different @code{make} programs have incompatible suffix lists and
80 of the source code.  Without one of these prefixes, the current search
97 When using GNU @code{make}, relying on @samp{VPATH} to find the source
99 since the @code{make} automatic variable @samp{$<} will represent the
100 source file wherever it is.  (Many versions of @code{make} set @samp{$<}
140 subtargets) work correctly with a parallel @code{make}.
146 @code{configure}) to run in @code{sh}, not in @code{csh}.  Don't use any
147 special features of @code{ksh} or @code{bash}.
149 The @code{configure} script and the Makefile rules for building and
161 The compression program @code{gzip} can be used in the @code{dist} rule.
171 and related programs, but should do so via @code{make} variables so that the
180 Use the following @code{make} variables to run those programs:
187 When you use @code{ranlib} or @code{ldconfig}, you should make sure
214 Thus, if you use Bison, have a variable named @code{BISON} whose default
216 @code{$(BISON)} whenever you need to use Bison.
218 File management utilities such as @code{ln}, @code{rm}, @code{mv}, and
225 example, @code{BISONFLAGS}.  (The names @code{CFLAGS} for the C
226 compiler, @code{YFLAGS} for yacc, and @code{LFLAGS} for lex, are
228 Use @code{CPPFLAGS} in any compilation command that runs the
229 preprocessor, and use @code{LDFLAGS} in any compilation command that
230 does linking as well as in any direct use of @code{ld}.
233 compilation of certain files, do not include them in @code{CFLAGS}.
234 Users expect to be able to specify @code{CFLAGS} freely themselves.
236 independently of @code{CFLAGS}, by writing them explicitly in the
246 Do include the @samp{-g} option in @code{CFLAGS}, because that is not
250 in the default value of @code{CFLAGS} as well.
252 Put @code{CFLAGS} last in the compilation command, after other variables
253 containing compiler options, so the user can use @code{CFLAGS} to
256 @code{CFLAGS} should be used in every invocation of the C compiler,
259 Every Makefile should define the variable @code{INSTALL}, which is the
262 Every Makefile should also define the variables @code{INSTALL_PROGRAM}
263 and @code{INSTALL_DATA}.  (The default for @code{INSTALL_PROGRAM} should
264 be @code{$(INSTALL)}; the default for @code{INSTALL_DATA} should be
265 @code{$@{INSTALL@} -m 644}.)  Then it should use those variables as the
274 Optionally, you may prepend the value of @code{DESTDIR} to the target
277 set the value of @code{DESTDIR} in your Makefile, and do not include it
278 in any installed files.  With support for @code{DESTDIR}, the above
313 @table @code
317 below.  The default value of @code{prefix} should be @file{/usr/local}.
322 Running @samp{make install} with a different value of @code{prefix} from
329 variables listed below.  The default value of @code{exec_prefix} should
330 be @code{$(prefix)}.
333 Generally, @code{$(exec_prefix)} is used for directories that contain
335 while @code{$(prefix)} is used directly for other directories.
337 Running @samp{make install} with a different value of @code{exec_prefix}
344 @table @code
473 header files in two places, one specified by @code{includedir} and one
474 specified by @code{oldincludedir}.
482 @code{oldincludedir} is empty.  If it is, they should not try to use
488 file in the @code{oldincludedir} directory if either (1) there is no
493 string in the file---part of a comment---and @code{grep} for that string.
508 write it as @samp{@@infodir@@}.)  @code{infodir} is separate from
509 @code{docdir} for compatibility with existing practice.
517 formats.)  They should all be set to @code{$(docdir)} by default.  (If
525 The directory for object files and libraries of object code.  Do not
527 instead.  The value of @code{libdir} should normally be
593 variable is normally inserted by the @code{configure} shell script.
619 should write the @code{install} rule to create these subdirectories.
651 use the @code{install-strip} target to do that.
653 If possible, write the @code{install} target rule so that it does not
660 specified as the values of the variables @code{prefix} and
661 @code{exec_prefix}, as well as all subdirectories that are needed.
662 One way to do this is by means of an @code{installdirs} target
666 @code{make} will ignore any errors.  This is in case there are systems
670 with @code{$(INSTALL_DATA)} (@pxref{Command Variables}), and then run
671 the @code{install-info} program if it is present.  @code{install-info}
697 When writing the @code{install} target, you must classify all the
709 must be installed by the @code{install} target.
714 such as @code{htmldir}.  As one example, if your package has multiple
716 (such as the ``split'' mode output by @code{makeinfo --html}), you'll
731 Like @code{install}, but strip the executable files while installing
732 them.  In simple cases, this target can use the @code{install} target in
742 @code{install-strip} target can't just refer to the @code{install}
745 @code{install-strip} should not strip the executables in the build
785 This typically includes everything deleted by @code{distclean}, plus
797 @code{maintainer-clean} should delete everything else that can be
808 @code{maintainer-clean} target should start with these two:
831 You must define the variable @code{MAKEINFO} in the Makefile.  It should
832 run the @code{makeinfo} program, which is part of the Texinfo
856 You must define the variable @code{TEXI2DVI} in the Makefile.  It should
857 run the program @code{texi2dvi}, which is part of the Texinfo
858 distribution.@footnote{@code{texi2dvi} uses @TeX{} to do the real work
860 write just the dependencies, and allow GNU @code{make} to provide the command.
872 Again, you would define the variable @code{TEXI2HTML} in the Makefile;
873 for example, it might run @code{makeinfo --no-split --html}
886 named, use @code{ln} or @code{cp} to install the proper files in it, and
887 then @code{tar} that subdirectory.
889 Compress the tar file with @code{gzip}.  For example, the actual
892 The @code{dist} target should explicitly depend on all non-source files
912 @table @code
959 When writing the @code{install} target, you must classify all the
975 @code{install-info}.  This cannot be done with a normal command, since
984 To classify the commands in the @code{install} rule into these three
1004 If you don't use a category line at the beginning of the @code{install}
1009 These are the category lines for @code{uninstall}:
1020 If the @code{install} or @code{uninstall} target has any dependencies