Difference between revisions of "Build"

From Linuxintro
imported>ThorstenStaerk
imported>ThorstenStaerk
Line 18: Line 18:
 
So, if you are asked how to write a Makefile, the best answer is "not at all, better have configure write the Makefile.
 
So, if you are asked how to write a Makefile, the best answer is "not at all, better have configure write the Makefile.
  
== See also ==
+
== make ==
* [[make]]
+
make is part of the build process, it does the compiling and linking.

Revision as of 10:56, 6 April 2009

Building typically involves the steps

automake
configure
make
make install

there are reasons not to count the "make install" step to the build, but it shall be mentioned here for clarity. Mostly, the automake step is done before bundling and publishing the software so the normal user does not need to do it. There are different files involved into the build process, the following gives an overview about that:

(you)-> Makefile.am -(automake)-> Makefile.in -
                                                \
                                                 -(configure)-> Makefile -
                                                /                          \
                         (you)-> configure.in -                             -(make)-> binary
                                                                           /
                                                      (you)-> sourcecode -

You as a developer write the sourcecode, the configure.in file and the Makefile.am. Makefile.am is transformed by automake to Makefile.in. Makefile.in and configure.in are transformed by configure to Makefile, while the Makefile and the sourcecode together build the binary. So, if you are asked how to write a Makefile, the best answer is "not at all, better have configure write the Makefile.

make

make is part of the build process, it does the compiling and linking.