Configure script: Difference between revisions

Revision as of 15:39, 14 March 2007

Revision as of 16:03, 14 March 2007

Line 2:

[[Image:Autoconf.svg|thumb|300px|Flow diagram including [[Configure (computing)|configure]], [[autoconf]] and [[automake]], three tools in the GNU build system]]

[[Configure (computing)|configure]] scripts are thegenerated output ofby the [[Autotools]] suite of build management tools. ManyThese popularscripts piecesquery the system on which they run for environment settings, platform architecture, and the existence and ___location of [[Freerequired Software]]build and runtime dependencies. They then use the gathered [[ProprietaryIntelligence Software(information gathering)|intel]] useto configureprocess scriptsand duringfill theirout systemtemplates, detectioncustomarily andending in <code>.in</code>. After successful completion, it is common for [[MakefileConfigure (computing)|configure]] generationto print a report to the developer invoking phasethem.

Because of the platform independence and broad developer experience with the [[Configure (computing)|configure]] script interface, many popular pieces of [[Free Software]] and [[Proprietary Software]] use this system during their system detection and [[Makefile]] generation phase. After [[Configure (computing)|configure]] scripts have been created, building software that makes use of them is as simple as

<code>./configure && make && make install </code>

=== Free Software that uses [[Configure (computing)|configure]] ===