Lines Matching full:files
39 * Files:: Files.
60 which files the developer must write, which files are machine generated
219 * It keeps the files generated during the build from cluttering up
222 * It permits you to remove the built files by simply removing the
235 copy the programs and any required support files to the "installation
239 In the Cygnus tree at present, the info files are built and
241 install them, run `make install-info'. The equivalent html files are
242 also built and installed in a separate step. To build the html files,
243 run `make html'. To install the html files run `make install-html'.
256 independent files such as info files.
260 files such as executables.
275 File: configure.info, Node: Getting Started, Next: Files, Prev: Introduction, Up: Top
281 package, you must write three files, and you must run some tools to
282 manually generate additional files.
289 * Generate files:: Generate files.
304 presence of particular header files or functions.
366 required to enable automatic rebuilding of generated files used by
370 If this macro is not used, then the generated files will always be
379 files. Other programs may or may not use one of them.
403 can be found in various `configure.in' files for libraries that are
428 compiling, which directs the libc header files to provide the
436 files in different directories. If your package lives entirely in
528 File: configure.info, Node: Write acconfig.h, Next: Generate files, Prev: Write Makefile.am, Up: Getting Started
568 File: configure.info, Node: Generate files, Next: Getting Started Example, Prev: Write acconfig.h, Up: Getting Started
570 2.4 Generate files
575 produce the first versions of the generated files. This is done by
591 running `automake' command in order to copy the required support files
599 support files into your directory.
606 generated files.
608 After doing that, whenever you have changed some of the input files
609 and want to regenerated the other files, go to your object directory
611 files manually, because there are complex order dependencies and it is
615 File: configure.info, Node: Getting Started Example, Prev: Generate files, Up: Getting Started
636 * Generate Files in Example:: Generate Files.
784 # Uncomment this if you have the standard ANSI/ISO C header files.
832 File: configure.info, Node: Getting Started Example 3, Next: Generate Files in Example, Prev: Getting Started Example 2, Up: Getting Started Example
906 File: configure.info, Node: Generate Files in Example, Prev: Getting Started Example 3, Up: Getting Started Example
908 2.5.4 Generate Files
911 We must now generate the other files, using the following commands.
921 When we run `automake', it will want to add some files to our
926 will want us to create certain additional files; as of this writing, it
928 are files which should appear in a standard GNU distribution. We can
929 either add those files, or run `automake' with the `--foreign' option.
931 Running these tools will generate the following files, all of which
945 File: configure.info, Node: Files, Next: Configuration Names, Prev: Getting Started, Up: Top
947 3 Files
951 uses a number of different files. The developer must write a few files.
955 ways. In describing the files that it uses, I will describe the common
960 * Developer Files:: Developer Files.
961 * Build Files:: Build Files.
962 * Support Files:: Support Files.
965 File: configure.info, Node: Developer Files, Next: Build Files, Up: Files
967 3.1 Developer Files
970 This section describes the files written or generated by the developer
975 * Developer Files Picture:: Developer Files Picture.
976 * Written Developer Files:: Written Developer Files.
977 * Generated Developer Files:: Generated Developer Files.
980 File: configure.info, Node: Developer Files Picture, Next: Written Developer Files, Up: Developer Files
982 3.1.1 Developer Files Picture
985 Here is a picture of the files which are written by the developer, the
986 generated files which would be included with a complete source
987 distribution, and the tools which create those files. The file names
1010 File: configure.info, Node: Written Developer Files, Next: Generated Developer Files, Prev: Developer Files Picture, Up: Developer Files
1012 3.1.2 Written Developer Files
1015 The following files would be written by the developer.
1022 an `AC_OUTPUT' macro listing which files to create when the
1057 files in that directory.
1063 File: configure.info, Node: Generated Developer Files, Prev: Written Developer Files, Up: Developer Files
1065 3.1.3 Generated Developer Files
1068 The following files would be generated by the developer.
1070 When using automake, these files are normally not generated manually
1072 to automatically rebuild the files as required. When
1126 File: configure.info, Node: Build Files, Next: Support Files, Prev: Developer Files, Up: Files
1128 3.2 Build Files
1131 This section describes the files which are created at configure and
1132 build time. These are the files which somebody who builds the package
1136 distinction between developer files and build files is not that the
1137 developer does not see the build files, but that somebody who only
1138 builds the package does not have to worry about the developer files.
1142 * Build Files Picture:: Build Files Picture.
1143 * Build Files Description:: Build Files Description.
1146 File: configure.info, Node: Build Files Picture, Next: Build Files Description, Up: Build Files
1148 3.2.1 Build Files Picture
1151 Here is a picture of the files which will be created at build time.
1153 to create other files, and the picture attempts to show that.
1166 File: configure.info, Node: Build Files Description, Prev: Build Files Picture, Up: Build Files
1168 3.2.2 Build Files Description
1171 This is a description of the files which are created at build time.
1180 necessary to recreate certain files if their inputs change.
1213 File: configure.info, Node: Support Files, Prev: Build Files, Up: Files
1215 3.3 Support Files
1218 The GNU configure and build system requires several support files to be
1224 You don't have to put the support files in the top level directory.
1229 In this section, I describe the support files, so that you can know
1253 Used to compile Emacs LISP files.
1270 version numbers for texinfo files.
1283 Required if you have any texinfo files. This is used when
1284 converting Texinfo files into DVI using `texi2dvi' and TeX.
1289 default to producing output files with a fixed name, and the
1294 File: configure.info, Node: Configuration Names, Next: Cross Compilation Tools, Prev: Files, Up: Top
1727 target compiler. There may not be any startup files or libraries for
1728 this target compiler. In fact, those files will probably be built as
1816 This is because the files in `libiberty' are used when building the
1942 so forth, as well as libraries and include files for the host system.
2163 files, those files will be on the build system. Whatever you determine
2164 based on those files may or may not be the case on the host system.
2220 files, such as `rtl.c', must be compiled into both subsidiary programs
2253 Cygnus configure does not use any generated files; there is no program
2312 particular host or target. They serve to select particular files to
2334 `files' and `links'. Cygnus configure will set up symlinks from the
2335 names in `links' to the files named in `files'. This is similar to the
2559 regenerate all files (`Makefile', `config.h', etc.) based on the
2561 because it isn't always necessary to regenerate all the files
2564 `CONFIG_FILES' and `CONFIG_HEADERS' to only regenerate files as
2617 * acconfig.h: Written Developer Files.
2620 * acinclude.m4: Written Developer Files.
2622 * aclocal.m4: Generated Developer Files.
2642 * config.cache: Build Files Description.
2644 * config.h: Build Files Description.
2646 * config.h.in: Generated Developer Files.
2648 * config.in: Generated Developer Files.
2650 * config.status: Build Files Description.
2655 * configure: Generated Developer Files.
2663 * configure.in: Written Developer Files.
2689 * Makefile: Build Files Description.
2692 * Makefile.am: Written Developer Files.
2695 * Makefile.in: Generated Developer Files.
2698 * stamp-h: Build Files Description.
2700 * stamp-h.in: Generated Developer Files.
2723 Node: Generate files23098
2728 Node: Generate Files in Example33099
2729 Node: Files34189
2730 Node: Developer Files34800
2731 Node: Developer Files Picture35180
2732 Node: Written Developer Files36468
2733 Node: Generated Developer Files39020
2734 Node: Build Files42164
2735 Node: Build Files Picture42825
2736 Node: Build Files Description43589
2737 Node: Support Files45595
