Lines Matching full:configure
3615 `configure'. This script is given arguments which describe the kind of
3617 `configure' script must record the configuration options so that they
3621 `configure' script in GNU packages. Many packages implement it using
3625 `configure' be a wrapper around a completely different configuration
3628 Another way for the `configure' script to operate is to make a link
3635 Another thing that `configure' can do is to edit the Makefile. If
3641 If `configure' does write the `Makefile', then `Makefile' should
3642 have a target named `Makefile' which causes `configure' to be rerun,
3644 that `configure' reads should be listed as dependencies of `Makefile'.
3646 All the files which are output from the `configure' script should
3648 automatically using `configure'. This is so that users won't think of
3651 The `configure' script should write a file named `config.status'
3656 The `configure' script should accept an option of the form
3662 If the user does not specify `--srcdir', then `configure' should
3671 `configure' can add to the Makefile a variable named `srcdir' whose
3674 In addition, the `configure' script should take options
3683 The `configure' script should also take an argument which specifies
3692 The `configure' script needs to be able to decode all plausible
3700 The `configure' script should also take the option
3702 argument. For example, `configure --build=i686-pc-linux-gnu' is
3703 equivalent to `configure i686-pc-linux-gnu'. When the build type is
3704 not specified by an option or argument, the `configure' script should
3714 Configure the package to build and install an optional user-level
3726 The package PACKAGE will be installed, so configure this package
3739 process. For example, the user could issue `configure CFLAGS=-g
3743 Specifying variables as arguments to `configure', like this:
3744 ./configure CC=gcc
3746 CC=gcc ./configure
3750 All `configure' scripts should accept all of the "detail" options
3754 will be able to configure an entire GNU source tree at once with a
3767 The `configure' script should normally treat the specified type of
3772 build type, use the configure option `--host=HOSTTYPE', where HOSTTYPE
3776 To configure a cross-compiler, cross-assembler, or what have you, you
3777 should specify a target different from the host, using the configure
3781 ./configure --host=HOSTTYPE --target=TARGETTYPE
3789 your program is set up to do this, your `configure' script can simply
3848 `configure'. A rule of the form:
3900 `configure') to run in `sh', not in `csh'. Don't use any special
3903 The `configure' script and the Makefile rules for building and
4083 (e.g., `make prefix=/usr install' or `configure' (e.g., `configure
4214 should never need to modify files in this directory to configure
4302 your `configure.in' file:
4355 variable is normally inserted by the `configure' shell script.
4556 `make maintainer-clean' should not delete `configure' even if
4557 `configure' can be remade using a rule in the Makefile. More
4559 needs to exist in order to run `configure' and then begin to build
5525 * configure: Configuration. (line 6)
5617 * optional features, configure-time: Configuration. (line 100)
