Lines Matching full:makefile
4 @node Makefile Conventions
5 @chapter Makefile Conventions
7 @cindex makefile, conventions for
35 Using Automake will help you write a Makefile that follows these
39 * Makefile Basics:: General Conventions for Makefiles
48 @node Makefile Basics
51 Every Makefile should contain this line:
65 suffixes you need in the particular Makefile, like this:
74 suffixes which may be subject to implicit rules in this Makefile.
101 only in implicit rules.) A Makefile target like
131 build directory. So Makefile rules to update them should put the
135 Makefile should not put it in the source directory, because building a
145 Write the Makefile commands (and any shell scripts, such as
149 The @code{configure} script and the Makefile rules for building and
170 The Makefile rules for building and installation can also use compilers
203 It is ok to use other utilities in Makefile portions (or scripts)
259 Every Makefile should define the variable @code{INSTALL}, which is the
262 Every Makefile should also define the variables @code{INSTALL_PROGRAM}
277 set the value of @code{DESTDIR} in your Makefile, and do not include it
481 The Makefile commands should check whether the value of
760 are created by this makefile. However, don't delete the files that
770 makefile) that are created by configuring or building the program. If
784 Delete almost everything that can be reconstructed with this Makefile.
791 if @file{configure} can be remade using a rule in the Makefile. More
831 You must define the variable @code{MAKEINFO} in the Makefile. It should
856 You must define the variable @code{TEXI2DVI} in the Makefile. It should
872 Again, you would define the variable @code{TEXI2HTML} in the Makefile;
993 @emph{should not} define them in the makefile).
