Lines Matching full:makefile
1536 `makefile'
3596 that it can be configured to run on a variety of systems. Your Makefile
3605 * Makefile Conventions:: Makefile conventions.
3609 File: standards.info, Node: Configuration, Next: Makefile Conventions, Up: Managing Releases
3635 Another thing that `configure' can do is to edit the Makefile. If
3637 `Makefile'. Instead, it should include a file `Makefile.in' which
3641 If `configure' does write the `Makefile', then `Makefile' should
3642 have a target named `Makefile' which causes `configure' to be rerun,
3644 that `configure' reads should be listed as dependencies of `Makefile'.
3669 definition of `VPATH' into the Makefile. Some rules may need to refer
3671 `configure' can add to the Makefile a variable named `srcdir' whose
3793 File: standards.info, Node: Makefile Conventions, Next: Releases, Prev: Configuration, Up: Managing Releases
3795 7.2 Makefile Conventions
3799 programs. Using Automake will help you write a Makefile that follows
3804 * Makefile Basics:: General conventions for Makefiles.
3814 File: standards.info, Node: Makefile Basics, Next: Utilities in Makefiles, Up: Makefile Conventions
3819 Every Makefile should contain this line:
3830 suffixes you need in the particular Makefile, like this:
3836 suffixes which may be subject to implicit rules in this Makefile.
3860 rules.) A Makefile target like
3882 build directory. So Makefile rules to update them should put the
3886 Makefile should not put it in the source directory, because building a
3894 File: standards.info, Node: Utilities in Makefiles, Next: Command Variables, Prev: Makefile Basics, Up: Makefile Conventions
3899 Write the Makefile commands (and any shell scripts, such as
3903 The `configure' script and the Makefile rules for building and
3918 The Makefile rules for building and installation can also use
3944 It is ok to use other utilities in Makefile portions (or scripts)
3949 File: standards.info, Node: Command Variables, Next: DESTDIR, Prev: Utilities in Makefiles, Up: Makefile Conventions
4001 Every Makefile should define the variable `INSTALL', which is the
4004 Every Makefile should also define the variables `INSTALL_PROGRAM'
4022 File: standards.info, Node: DESTDIR, Next: Directory Variables, Prev: Command Variables, Up: Makefile Conventions
4054 You should not set the value of `DESTDIR' in your `Makefile' at all;
4071 File: standards.info, Node: Directory Variables, Next: Standard Targets, Prev: DESTDIR, Up: Makefile Conventions
4246 The Makefile commands should check whether the value of
4394 File: standards.info, Node: Standard Targets, Next: Install Command Categories, Prev: Directory Variables, Up: Makefile Conventions
4525 directories if they are created by this makefile. However, don't
4536 makefile) that are created by configuring or building the program.
4551 Makefile. This typically includes everything deleted by
4557 `configure' can be remade using a rule in the Makefile. More
4591 You must define the variable `MAKEINFO' in the Makefile. It should
4618 You must define the variable `TEXI2DVI' in the Makefile. It should
4630 Again, you would define the variable `TEXI2HTML' in the Makefile;
4701 File: standards.info, Node: Install Command Categories, Prev: Standard Targets, Up: Makefile Conventions
4741 _should not_ define them in the makefile).
4805 File: standards.info, Node: Releases, Prev: Makefile Conventions, Up: Managing Releases
4823 files by programs under the control of the Makefile.
5527 * conventions for makefiles: Makefile Conventions.
5596 * makefile, conventions for: Makefile Conventions.
5654 * standards for makefiles: Makefile Conventions.
5730 Node: Makefile Conventions129738
5731 Node: Makefile Basics130620
