Lines Matching full:makefile
3105 Autoconf macros and Makefile fragments used throughout the tree.
3216 * Makefile:: Targets in `gcc/Makefile'.
3351 * `Makefile' is constructed from `Makefile.in', together with the
3352 host and target fragments (*note Makefile Fragments: Fragments.)
3354 Makefile fragments `LANGUAGE/Make-lang.in'.
3374 The following configuration headers are created from the Makefile,
3396 File: gccint.info, Node: Build, Next: Makefile, Prev: Configuration, Up: gcc Directory
3407 File: gccint.info, Node: Makefile, Next: Library Files, Prev: Build, Up: gcc Directory
3409 6.3.4 Makefile Targets
3481 directory, but rather a complex Makefile that coordinates the various
3592 File: gccint.info, Node: Library Files, Next: Headers, Prev: Makefile, Up: gcc Directory
3619 installed in `LIBSUBDIR/include', unless the target Makefile fragment
3696 `texi2dvi' (via the Makefile macro `$(TEXI2DVI)'). PDF-formatted
3698 Makefile macro `$(TEXI2PDF)'). HTML formatted manuals are generated by
3701 directory, using `makeinfo' via the Makefile macro `$(MAKEINFO)', and
3862 * Check targets in `Makefile.def' for the top-level `Makefile' to
3905 * Front End Makefile:: The front end `Make-lang.in' file.
3926 Front End `Make-lang.in' File: Front End Makefile, for details of
3943 File: gccint.info, Node: Front End Config, Next: Front End Makefile, Prev: Front End Directory, Up: Front End
3973 top level `Makefile' to build the runtime libraries for this
4001 mechanism can be used to create a file `LANGUAGE/Makefile' from
4002 `LANGUAGE/Makefile.in', but this is deprecated, building
4003 everything from the single `gcc/Makefile' is preferred.
4013 File: gccint.info, Node: Front End Makefile, Prev: Front End Config, Up: Front End
4021 Makefile rules required to build those targets (which may if necessary
4024 can use the standard rule in `gcc/Makefile.in' to the variable
4124 Functions: Target Macros.), possibly a target Makefile fragment
4125 `t-MACHINE' (*note The Target Makefile Fragment: Target
25823 the target makefile fragment or if none of the options listed in
25914 automatically by `Makefile', and specify private search areas for
35558 it will also be necessary to add a rule to the makefile fragment
36359 19 Makefile Fragments
36363 the file `Makefile' from the template file `Makefile.in'. When it does
36364 this, it can incorporate makefile fragments from the `config'
36365 directory. These are used to set Makefile parameters that are not
36388 19.1 Target Makefile Fragments
36391 Target makefile fragments can set these Makefile variables.
36445 msoft-float', `Makefile' will build special versions of `libgcc.a'
36505 `Makefile' rule to generate the `specs' file that's going to be
36517 19.2 Host Makefile Fragments
36521 for makefile dependencies.
36978 `GTFILES' variable in `Makefile.in'.
37005 `Makefile'!
37466 The following GNU Makefile excerpt shows how to build a simple plugin:
37566 the parallelism is facilitated via generating a `Makefile', it
45382 * host makefile fragment: Host Fragment. (line 6)
45703 * makefile fragment: Fragments. (line 6)
45704 * makefile targets: Makefile. (line 6)
46695 * target makefile fragment: Target Fragment. (line 6)
47091 * targets, makefile: Makefile. (line 6)
47544 Node: Makefile167607
47545 Ref: Makefile-Footnote-1174410
47546 Ref: Makefile-Footnote-2174555
47556 Node: Front End Makefile191734
