Transferred from: http://blog.csdn.net/secondjanuary/article/details/8985795
- These are typical installation steps for programs that are generated using the GNU autoconf and Automake
- Config/configure/configure
- This is used to detect the target characteristics of your installation platform. For example, it detects if you have CC or GCC, does not need CC or GCC, it is a shell script
- This step is generally used to generate Makefile, to prepare for the next compilation, you can control the installation by adding parameters after the Configure, such as:
- ./configure--PREFIX=/USR
- The above means that the software is installed in/usr below
- The execution file will be installed in/usr/bin (not the default/usr/local/bin)
- The resource file will be installed in/usr/share (not the default/usr/local/share)
- At the same time some software configuration files can be set by specifying the--sys-config= parameter
- There are also such parameters as:--with 、--enable 、--without 、--disable and so on, you can control the compilation with the./configure--help to see detailed instructions to help
- Make
- This step is compiled, it reads the instruction from the makefile, and then compiles the
- This step is compiled, and most of the source code packages are compiled in this step
- Of course, some perl or Python-written software needs to call Perl or Python to compile
- If error occurs during the make process, you need to write down the error code (note that it is not just the last line), and then you can submit a bugreport to the developer (usually with a submit address in the INSTALL), or your system will have fewer dependent libraries, which requires careful study of the error code.
- Make Test/make Check
- As the name implies, this step is to check the previous make, to ensure there is no error, that is, this step of test, check to all OK, error 0
- sudo make install
- This step is for installation, it also reads instructions from makefile, installs to the specified location
- This command to install, generally requires that you have root permissions (because you want to write to the system file), so the previous use of sudo
- Automake and autoconf are very useful things to publish C programs. If you also write programs that want to use Automake and autoconf, you can refer to the relevant articles on cngnu.org
[Turn] Linux under Config/configure/configure, make, make test/make check, sudo make install function
