Lines Matching refs:files
127 GNU distributions usually contain some files which are not source
128 files---for example, Info files, and the output from Autoconf, Automake,
129 Bison or Flex. Since these files normally appear in the source
132 updated files in the source directory.
233 compilation of certain files, do not include them in @code{CFLAGS}.
278 in any installed files. With support for @code{DESTDIR}, the above
334 machine-specific files (such as executables and subroutine libraries),
375 Data files used by the program during its execution are divided into
380 Some files are normally modified by programs; others are never normally
384 Some files are architecture-independent and can be shared by all
391 discourage the use of architecture-dependent files, aside from object
392 files and libraries. It is much cleaner to make other data files
396 to put these various kinds of files in:
401 data files. This should normally be @file{/usr/local/share}, but
409 architecture-independent data files for this program. This is usually
411 variables so that you can move these program-specific files without
412 altering the location for Info files, man pages, etc.
423 The directory for installing read-only data files that pertain to a
424 single machine--that is to say, files for configuring a host. Mailer
425 and network configuration files, @file{/etc/passwd}, and so forth belong
426 here. All the files in this directory should be ordinary ASCII text
427 files. This directory should normally be @file{/usr/local/etc}, but
433 files that are modified in the normal course of their use (programs
438 The directory for installing architecture-independent data files which
444 The directory for installing data files which the programs modify while
446 need to modify files in this directory to configure the package's
447 operation; put such configuration information in separate files that go
455 types of files, if your program has them. Every GNU package should
456 have Info files, so every program needs @samp{infodir}, but not all
462 The directory for installing header files to be included by user
468 Most compilers other than GCC do not look for header files in directory
469 @file{/usr/local/include}. So installing the header files this way is
473 header files in two places, one specified by @code{includedir} and one
477 The directory for installing @samp{#include} header files for use with
483 it; they should cancel the second installation of the header files.
496 The directory for installing documentation files (other than Info) for
501 may include a version number, prevents collisions among files with
505 The directory for installing the Info files for this package. By
515 Directories for installing documentation files in the particular
525 The directory for object files and libraries of object code. Do not
532 The directory for installing any Emacs Lisp files in this package. By
612 # Where to put the Info files.
616 If your program installs a large number of files into one of the
636 target need not rebuild any documentation files; Info files should
637 normally be included in the distribution, and DVI files should be made
658 The commands should create all the directories in which files are to be
669 The way to install Info files is to copy them into @file{$(infodir)}
708 package, if that format is desired. GNU prefers Info files, so these
711 When you have many documentation files to install, we recommend that
715 manuals, and you wish to install HTML documentation with many files
721 Delete all the installed files---the copies that the @samp{install}
725 only the directories where files are installed.
731 Like @code{install}, but strip the executable files while installing
758 Delete all files in the current directory that are normally created by
759 building the program. Also delete files in other directories if they
760 are created by this makefile. However, don't delete the files that
761 record the configuration. Also preserve files that could be made by
766 Delete @file{.dvi} files here if they are not part of the distribution.
769 Delete all files in the current directory (or created by this
772 any other files, @samp{make distclean} should leave only the files
778 Like @samp{clean}, but may refrain from deleting a few files that people
786 more: C source files produced by Bison, tags tables, Info files, and
802 reconstruct some of the files that @samp{make maintainer-clean} deletes.
803 Since these files are normally included in the distribution, we don't
812 @@echo 'deletes files that may need special tools to rebuild.'
820 Generate any Info files needed. The best way to write the rules is as
835 Normally a GNU distribution comes with Info files, and that means the
836 Info files are present in the source directory. Therefore, the Make
838 users build the package, ordinarily Make will not update the Info files
845 Generate documentation files in the given format, if possible.
846 Here's an example rule for generating DVI files from Texinfo:
886 named, use @code{ln} or @code{cp} to install the proper files in it, and
892 The @code{dist} target should explicitly depend on all non-source files
920 directories where files are installed, and their parent directories.
963 Normal commands move files into their proper places, and set their
964 modes. They may not alter any files except the ones that come entirely
967 Pre-installation and post-installation commands may alter other files;
968 in particular, they can edit global configuration files or data bases.
979 installs the package's Info files.
1041 executables and other files that need to be installed, and has its own