Lines Matching full:files
78 diff to the `standards.texi' or `make-stds.texi' files, but if you
79 don't have those files, please mail your suggestion anyway.
131 recently than the Unix program. Eliminate use of temporary files. Do
141 other funny characters in the input files. Add a programming language
172 This also applies to comments and documentation files. For copyright
227 names), we abbreviate it to "w". For instance, the files and functions
319 files), and it is done poorly in Unix, feel free to replace it
399 benefit of prototypes in all the files where the function is called.
495 * File Usage:: Which files to use, and where.
551 including file names, lines, files, and symbols, by allocating all data
555 Utilities reading files should not drop NUL characters, or any other
600 files in a directory, use `readdir' or some other high-level interface.
628 If you make temporary files, check the `TMPDIR' environment
633 creating temporary files in world-writable directories. In C, you can
634 avoid this problem by creating temporary files in this manner:
667 other libraries. These can go in the same files with user entry points
703 When an error is spread over several files, you can use this format:
819 to be input files only; any output files would be specified using
908 line. (The rules are different for copyright notices in source files;
1220 `elide-empty-files'
1296 `files-from'
1305 `fixed-output-files'
1461 `keep-files'
1838 `report-identical-files'
1875 Used by `recode' to chose files or pipes for sequencing passes.
1917 `speed-large-files'
1999 `text-files'
2104 impractical for other reasons to operate on files more than a few meg
2105 long, it is reasonable to read entire input files into memory to
2109 operate on very large files, it is important to avoid using a technique
2110 that would artificially limit the size of files it can handle. If a
2112 input files, it should keep only a line in memory, because this is not
2113 very hard and users will want to be able to operate on input files that
2126 read-only file systems. Thus, if the program manages log files, lock
2127 files, backup files, score files, or any other files which are modified
2128 for internal purposes, these files should not be stored in `/usr' or
2133 files in `/etc' when its job is to update the system configuration.
2135 is reasonable for the program to store other files in the same
2152 * Names:: Naming variables, functions, and files.
2486 5.4 Naming Variables, Functions, and Files
2522 conflict if the files were loaded onto an MS-DOS file system which
2576 Windows-specific files, but the macro for Windows conditionals is
2580 when compiling your C files. When you compile on GNU or GNU/Linux,
2661 source files `error.c' and `error.h' from the Gnulib library source
2715 files
2736 can declare them in other files without any risk of type conflict.
2742 these declarations in configuration files specific to those
2891 printf ((nfiles != 1 ? gettext ("%d files processed")
2900 printf (ngettext ("%d files processed", "%d file processed", nfiles),
2961 Don't assume that `mmap' either works on all files or fails for all
2962 files. It may work on some files and fail on others.
2970 different kinds of "ordinary files." Many of them support `mmap', but
2972 of files.
2993 * NEWS File:: NEWS files supplement manuals.
3047 manual for "comparison of files" which covers both of those programs,
3243 files. The purpose of this is so that people investigating bugs in the
3288 files (manuals, help files, etc.) in change logs. However, we've been
3389 documentation files. This is because documentation is not susceptible
3396 However, you should keep change logs for documentation files when the
3507 There may be non-free books or documentation files that describe the
3525 Making a release is more than just bundling up your source files in a
3566 setting up the same configuration that was set up last time. The files
3569 All the files which are output from the `configure' script should
3647 find certain files. That is outside the scope of what `--with'
3792 GNU distributions usually contain some files which are not source
3793 files--for example, Info files, and the output from Autoconf, Automake,
3794 Bison or Flex. Since these files normally appear in the source
3797 updated files in the source directory.
3891 compilation of certain files, do not include them in `CFLAGS'. Users
3929 target files, as explained in the next section.
3962 provides for "staged installs", where the installed files are not
3964 into a temporary location (`DESTDIR'). However, installed files
3969 then the files are installed into their expected locations by default.
4026 machine-specific files (such as executables and subroutine
4062 Data files used by the program during its execution are divided into
4065 * Some files are normally modified by programs; others are never
4068 * Some files are architecture-independent and can be shared by all
4074 discourage the use of architecture-dependent files, aside from object
4075 files and libraries. It is much cleaner to make other data files
4079 to put these various kinds of files in:
4083 architecture-independent data files. This should normally be
4091 architecture-independent data files for this program. This is
4094 files without altering the location for Info files, man pages, etc.
4105 The directory for installing read-only data files that pertain to a
4106 single machine-that is to say, files for configuring a host.
4107 Mailer and network configuration files, `/etc/passwd', and so
4108 forth belong here. All the files in this directory should be
4109 ordinary ASCII text files. This directory should normally be
4115 files that are modified in the normal course of their use (programs
4120 The directory for installing architecture-independent data files
4126 The directory for installing data files which the programs modify
4128 should never need to modify files in this directory to configure
4130 separate files that go in `$(datadir)' or `$(sysconfdir)'.
4136 types of files, if your program has them. Every GNU package should
4137 have Info files, so every program needs `infodir', but not all need
4141 The directory for installing header files to be included by user
4147 Most compilers other than GCC do not look for header files in
4148 directory `/usr/local/include'. So installing the header files
4152 They should install their header files in two places, one
4156 The directory for installing `#include' header files for use with
4162 it; they should cancel the second installation of the header files.
4175 The directory for installing documentation files (other than Info)
4180 version number, prevents collisions among files with common names,
4184 The directory for installing the Info files for this package. By
4194 Directories for installing documentation files in the particular
4203 The directory for object files and libraries of object code. Do
4210 The directory for installing any Emacs Lisp files in this package.
4284 # Where to put the Info files.
4287 If your program installs a large number of files into one of the
4317 This target need not rebuild any documentation files; Info files
4319 documentation format) files should be made only when explicitly
4341 The commands should create all the directories in which files are
4352 The way to install Info files is to copy them into `$(infodir)'
4387 the package, if that format is desired. GNU prefers Info files,
4390 When you have many documentation files to install, we recommend
4395 documentation with many files (such as the "split" mode output by
4404 Delete all the installed files--the copies that the `install' and
4408 done, only the directories where files are installed.
4415 Like `install', but strip the executable files while installing
4437 Delete all files in the current directory that are normally
4438 created by building the program. Also delete files in other
4440 delete the files that record the configuration. Also preserve
4441 files that could be made by building, but normally aren't because
4446 Delete `.dvi' files here if they are not part of the distribution.
4449 Delete all files in the current directory (or created by this
4452 creating any other files, `make distclean' should leave only the
4453 files that were in the distribution. However, there is no need to
4458 Like `clean', but may refrain from deleting a few files that people
4466 `distclean', plus more: C source files produced by Bison, tags
4467 tables, Info files, and so on.
4481 special tools to reconstruct some of the files that `make
4482 maintainer-clean' deletes. Since these files are normally
4491 @echo 'deletes files that may need special tools to rebuild.'
4497 Generate any Info files needed. The best way to write the rules
4509 Normally a GNU distribution comes with Info files, and that means
4510 the Info files are present in the source directory. Therefore,
4513 update the Info files because they will already be up to date.
4519 Generate documentation files in the given format. These targets
4525 Here's an example rule for generating DVI files from Texinfo:
4558 appropriately named, use `ln' or `cp' to install the proper files
4564 The `dist' target should explicitly depend on all non-source files
4584 directories where files are installed, and their parent
4624 Normal commands move files into their proper places, and set their
4625 modes. They may not alter any files except the ones that come entirely
4629 files; in particular, they can edit global configuration files or data
4641 installs the package's Info files.
4696 all the executables and other files that need to be installed, and has
4733 files contained in the distribution. This means that all the files
4735 files" and "non-source files". Source files are written by humans and
4736 never changed automatically; non-source files are produced from source
4737 files by programs under the control of the Makefile.
4754 Naturally, all the source files must be in the distribution. It is
4755 okay to include non-source files in the distribution, provided they are
4757 normally will never modify them. We commonly include non-source files
4762 Non-source files that might actually be modified by building and
4764 So if you do distribute non-source files, always make sure they are up
4770 permissions of the files from the tar archive will be able to extract
4771 all the files even if the user is unprivileged.
4773 Make sure that all the files in the distribution are world-readable.
4789 test print any `*.texinfo' or `*.texi' files.
4795 know what other files to get.
4856 can handle some kinds of files. However, `mplayer' recommends use of
4857 non-free codecs for other kinds of files, and users that install
5448 * names of variables, functions, and files: Names. (line 6)
5496 * temporary files: Semantics. (line 84)
