Configure script: Difference between revisions

Content deleted Content added
'just' is debatable -- usually must spend time hunting down missing depends first
m clean up; http->https (see this RfC) using AWB
Line 16:
Upon its completion, <code>configure</code> prints a report to <code>config.log</code>. Running <code>./configure --help</code> gives a list of command line arguments, for enabling or disabling additional features such as:
 
./configure --libsconfigure—libs="-lmpfr -lgmp"
./configure --prefixconfigure—prefix=/home/myname/apps
 
The first line includes the <code>mpfr</code> and <code>gmp</code> libraries. The second line tells [[make (software)|make]] to install the final version in <code>/home/myname/apps</code>. The <code>INSTALL</code> file contains instructions should the prescribed steps fail.
 
==Generating <code>configure</code>==
Software developers simplify the challenge of [[cross-platform]] software development by using GNU's [[Autotools]].<ref>{{cite web |url=httphttps://www.gnu.org/software/autoconf/ |title=Autoconf - GNU Project - Free Software Foundation (FSF) |publisher=GNU Operating System |accessdate=20 November 2010}}</ref> 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 <code>configure.ac</code> or the now deprecated <code>configure.in</code> to be read by <code>configure</code> during the installation phase.
 
== Dependency checking ==