Linux-Configurescript)

Linux-Configurescript)

Configure script)

From Wikipedia, the free encyclopedia

Originated from Wikipedia

A Configure script is an executable script designed to aid in developing a program to be run on a wide number of different computers. it matches the libraries on the user's computer, with those required by the program, just before compiling it from its source code.

The configuration script is an executable script that helps the program to run on different computers. Before compiling the source code of the configuration script, configure the script to match the library files required for running the program on your computer.

As a common practice, all configure scripts are named "configure". Usually, configure scripts are written for the Bourne shell, but they may be written for execution in any desired shell.

As a convention, all configuration scripts are named "configure ". The configuration script is usually written by the Bourne shell script, but the configuration script can also be written by any other version of the shell script language for execution.

Usage (Usage)

Obtaining software directly from the source code (a standard procedure on Unix computers) generally involves the following three steps: refreshing the makefile, compiling the code, and finally installing the executable in the appropriate places. A configure script accomplishes the first of these steps. using configure scripts is an automatic method of generating makefiles before compilation to tailor the software to the system on which the executable is to be compiled and run. the final executable software is most commonly obtained by executing the following commands in a shell that is currently pointing to the directory containing the source code:

Software directly generated by source code (standard procedures on Unix computers) usually involves the following three steps: configure the makefile file, compile the code, and finally install the executable program in the appropriate place. Configure the script to complete the first step in step 3. Before compiling software that has good compatibility with the system, using configuration scripts to generate makefile files is an automated method. Run the shell script containing the following commands in the source file directory to generate executable software.

One must type. /configure (dot slash configure) rather than simply configure to indicate to the shell that the script is in ". ", I. e. the current directory. by default, for security reasons, Unix operating systems do not search the current directory for executables so one must give the full path explicitly to avoid an error. [1]

You must add the dot and slash before configure./configure to tell the shell program where the configure script is located, such as in the current directory. By default, the Unix operating system does not search for executable files in the current directory. Therefore, a complete path must be provided to avoid errors.

Upon its completion, configure prints a report to config. log. Running./configure -- help gives a list of command line arguments, for enabling or disabling additional features such:

Once the configuration script is completed, it prints a report in config. log. Run./configure -- help to get a list of command line parameters, which enables additional functions:

The first line provided des the mpfr and gmp libraries. the second line tells make to install the final version in/home/myname/apps. note that if you have a space character in your argument, you will need to enclose the text in quotation marks as shown on the first line. the INSTALL file contains instructions shoshould the prescribed steps fail.

The first line contains the mpfr library file and the gmp library file. The second line is to install the final version in the path/home/myname/apps. Note: if there is a space between your parameters, You need to include the text content in double quotation marks as shown in the first line. If the installation file contains the installation instructions, the standard steps will not succeed.

Generating configure (generate configure)

Software developers simplify the challenge of cross-platform software development by using GNU's Autotools. [2] These scripts query the system on which they run for: environment settings, platform architecture, and the existence and location of required build and runtime dependencies. they store the gathered information in configure. ac or (the now deprecated) configure. in to be read by configure during the installation phase.

Software developers use the Autotools tool under GNU to reduce the difficulty of cross-platform software development. Script query: system settings, platform architecture, build, and runtime dependencies. The collected information will be stored in the configure. ac file or configure. in (which has been deprecated now) and used by configure during installation.

Dependency checking)

In new development, library dependency checking has been done in great part using pkg-config via the m4 macro, PKG_CHECK_MODULES. before pkg-config's gained popularity, separate m4 macros were created to locate files known to be attached ded in the distribution of libraries depended.

Latest Progress: library file dependency check can be completed by using the m4 macro and PKG_CHECK_MODULES modules in pkg-config. Before pkg-config was popularized, the independent m4 macro was created in the dependency library of the linux release version to locate the file.

History (History)

The first program to come with a Configure script was rn by Larry Wall in 1984. notable for its wry and jocular running commentary, that script was written entirely by hand still ves as part of the build system of the trn program.
The first program with script configuration was the rn developed by Larry Wall in 1984. It is ironic that this script is completely manually written and still exists as part of the loan program compilation system.

Since then, an ecosystem of programs has grown up to automate the creation of Configure scripts as far as possible, of which the most common is the GNU Autoconf system described above.

Since then, the program ecosystem has been upgraded to automatically generate configuration scripts as much as possible as the GNU Autoconf system mentioned above.