Lines Matching full:makefile
116 developer to write a simplified `Makefile'.
178 The new BSD make provides a standard library of Makefile fragments,
184 Makefile which could be used by the standard make program. In 1995, Tom
287 * Write Makefile.am:: Write Makefile.am.
293 File: configure.info, Node: Write configure.in, Next: Write Makefile.am, Up: Getting Started
435 should produce. This is normally a list of one or more `Makefile'
437 a single directory, you would use simply `AC_OUTPUT(Makefile)'.
439 `AC_OUTPUT(Makefile lib/Makefile)'.
445 put `ACLOCAL_AMFLAGS = -I m4' in your `Makefile.am' file so that the
453 File: configure.info, Node: Write Makefile.am, Next: Write acconfig.h, Prev: Write configure.in, Up: Getting Started
455 2.2 Write Makefile.am
458 You must write the file `Makefile.am'. This is an automake input file,
462 The automake commands in `Makefile.am' mostly look like variable
463 assignments in a `Makefile'. automake recognizes special variable
466 There will be one `Makefile.am' file for each directory in your
467 package. For each directory with subdirectories, the `Makefile.am'
472 For each `Makefile.am', there should be a corresponding `Makefile'
475 Every `Makefile.am' written at Cygnus should contain the line
484 `automake' and perhaps getting an invalid `Makefile.in'.
521 The `Makefile.am' file may also contain almost anything that may
522 appear in a normal `Makefile'. automake also supports many other
528 File: configure.info, Node: Write acconfig.h, Next: Generate files, Prev: Write Makefile.am, Up: Getting Started
573 Once you have written `configure.in', `Makefile.am', `acconfig.h', and
672 We also write a simple `Makefile'.
700 In our `Makefile', we don't provide any way to install the program.
777 Here is the associated `Makefile'. We've added support for the
818 on their systems, so that they can uncomment the `Makefile' correctly.
825 The use of `Makefile' variables like `CC', `CFLAGS' and `LDFLAGS'
839 than requiring the user to edit the `Makefile'. We will also write a
840 `Makefile.am' rather than a `Makefile'.
856 AC_OUTPUT(Makefile)
880 The new `Makefile.am' file is as follows. Note how simple this is
881 compared to our earlier `Makefile'.
940 * `Makefile.in'
991 acconfig.h configure.in Makefile.am
1000 | v | Makefile.in
1026 `Makefile.am'
1029 may also contain ordinary Makefile targets. This file is only
1032 which the developer writes `Makefile.in' directly). *Note Write
1033 Makefile.am::.
1055 -I m4' in `Makefile.am' to force `aclocal' to look there for macro
1071 after the first time. Instead, the generated `Makefile' contains rules
1087 `Makefile.in'
1089 `Makefile' at build time. This file is generated by `automake'
1090 from `Makefile.am'. If you aren't using automake, you must write
1091 this file yourself. This file is pretty much a normal `Makefile',
1155 config.in *configure* Makefile.in
1163 config.h Makefile
1178 `Makefile' derived from an automake generated `Makefile.in' will
1182 `Makefile'
1184 `config.status' script will transform `Makefile.in' into
1185 `Makefile'.
1237 Used by an automake generated `Makefile' if you put `ansi2knr' in
1238 `AUTOMAKE_OPTIONS' in `Makefile.am'. This permits compiling ANSI
1268 A shell script used by an automake generated `Makefile' to pretty
1274 used by an automake generated `Makefile' to avoid certain sorts of
1279 directories. This is used by an automake generated `Makefile'
1287 A shell script used by an automake generated `Makefile' to run
1622 Cygnus configure system, not autoconf. The top level `Makefile.in' is
1714 actually controlled by `Makefile' targets.
1781 The top level `Makefile' in the Cygnus tree defines targets for every
1785 the `Makefile' target `all-DIR' will build that library or program.
1790 `Makefile'.
1793 `Makefile' target `configure-target-DIR' will configure that library.
1794 The `Makefile' target `all-target-DIR' will build that library.
2198 The main Canadian Cross issue in a `Makefile' arises when you want to
2219 The gcc `Makefile.in' shows a complex situation in which certain
2294 variable is a list of subdirectories where a `Makefile.in' file may be
2295 found. Cygnus configure will automatically look for a `Makefile.in'
2300 For each `Makefile.in', Cygnus configure will automatically create a
2301 `Makefile' by adding definitions for `make' variables such as `host'
2308 the file into the generated `Makefile'. The file contents will be read
2309 in after the first line in `Makefile.in' which starts with `####'.
2311 These `Makefile' fragments are used to customize behaviour for a
2318 The `Makefile' fragment support is similar to the autoconf
2321 After creating each `Makefile', the post target script will be run
2323 the `Makefile'. When it is run, the shell variable `Makefile' will
2324 hold the name of the `Makefile', including the appropriate directory
2358 Most of the `Makefile' information is written out by the shell
2361 `Makefile' fragments. These fragments are then incorporated into the
2362 resulting `Makefile' by the Cygnus configure script.
2388 scripts and `Makefile's used for target libraries.
2402 `MULTILIB_OPTIONS' in the target `Makefile' fragment. Several other
2404 Makefile Fragment: (gcc)Target Fragment.
2434 invoked after the `Makefile' has been created by the `configure'
2436 modifies the `Makefile' to support multilibs.
2438 The `config-ml.in' script makes one copy of the `Makefile' for each
2444 `Makefile's. The `Makefile.in' must have definitions for these
2446 The `Makefile' should use default values for these variables which will
2462 In the top level `Makefile' only, `config-ml.in' will set this to
2473 In the top level `Makefile' only, `config-ml.in' will set these
2489 The `config-ml.in' script also modifies the top level `Makefile' to
2493 The default target of the `Makefile' should include the following
2500 in the top level `Makefile' if multilibs were enabled.
2502 The `install' target of the `Makefile' should include the following
2543 My `Makefile' has `@' characters in it.
2545 your `Makefile.in' without adding the appropriate `AC_SUBST' call
2547 rebuild `Makefile' in your build directory. To rebuild `Makefile'
2548 from `Makefile.in', run the shell script `config.status' with no
2551 automatically by `Makefile' targets, but if your `Makefile' has
2555 Normally, you don't; they will be run automatically by `Makefile'
2559 regenerate all files (`Makefile', `config.h', etc.) based on the
2562 after running `config.status --recheck'. The `Makefile' targets
2638 * canadian cross in makefile: CCross in Make. (line 6)
2689 * Makefile: Build Files Description.
2691 * Makefile, garbage characters: FAQ. (line 29)
2692 * Makefile.am: Written Developer Files.
2694 * Makefile.am, writing: Write Makefile.am. (line 6)
2695 * Makefile.in: Generated Developer Files.
2721 Node: Write Makefile.am18373
