Documentation/Maemo 5 Developer Guide/GNU Build System - Revision history

imported_>sicelo at 18:23, 13 October 2014

2014-10-13T18:23:05Z

← Older revision		Revision as of 18:23, 13 October 2014
Line 1,160:		Line 1,160:
	For the purpose of this example, only one macro is used, <code>PKG_CHECK_MODULES</code>, which is used as part of <code>configure.ac</code> for pkg-config integration		For the purpose of this example, only one macro is used, <code>PKG_CHECK_MODULES</code>, which is used as part of <code>configure.ac</code> for pkg-config integration

	<source lang="~~autoconf~~">		<source lang="text">
	# Check whether the necessary pkg-config packages are present. The		# Check whether the necessary pkg-config packages are present. The
	# PKG_CHECK_MODULES macro is supplied by pkg-config		# PKG_CHECK_MODULES macro is supplied by pkg-config

imported_>dukenukem at 18:58, 20 September 2012

2012-09-20T18:58:37Z

← Older revision		Revision as of 18:58, 20 September 2012
Line 1,178:		Line 1,178:
	# Makefile or supplied by the user running ./configure.		# Makefile or supplied by the user running ./configure.
	CFLAGS="$HHW_CFLAGS $CFLAGS"		CFLAGS="$HHW_CFLAGS $CFLAGS"
	LIBS="$HHW_LIBS $LIBS		LIBS="$HHW_LIBS $LIBS"
	</source>		</source>

imported_>amigadave: /* Checking for Distribution Sanity */ add link

2010-11-12T10:01:58Z

Checking for Distribution Sanity: add link

← Older revision		Revision as of 10:01, 12 November 2010
Line 1,119:		Line 1,119:
	To test whether building the software from the distribution tarball is possible, execute the distcheck-target. It first creates a distribution tarball, then extracts it in a new subdirectory, runs configure there and tries and builds the software with the default make target. If it fails, the relevant error is given.		To test whether building the software from the distribution tarball is possible, execute the distcheck-target. It first creates a distribution tarball, then extracts it in a new subdirectory, runs configure there and tries and builds the software with the default make target. If it fails, the relevant error is given.

	Making the distcheck target each time before making a dist target is recommended, so that you can be sure that the distribution tarball can be used outside the source tree. This step is especially critical later when making Debian packages.		Making the distcheck target each time before making a dist target is recommended, so that you can be sure that the distribution tarball can be used outside the source tree. This step is especially critical later when [[packaging\|making Debian packages]].

	=== Cleaning up ===		=== Cleaning up ===

imported_>amigadave: use and `, wikify slightly, add links to examples`


2010-11-12T09:58:09Z
use <source> and <code>, wikify slightly, add links to examples
Show changes



imported_>amigadave: use 

2010-09-07T15:04:46Z
use <code>

				
				
				
				
				
				← Older revision
				Revision as of 15:04, 7 September 2010
				
Line 1,150:
Line 1,150:
Pkg-config comes with a macro package ('''pkg.m4'''), which contains some useful macros for integration. The best documentation for these can be found in the pkg-config manual pages. Pkg-config comes with a macro package ('''pkg.m4'''), which contains some useful macros for integration. The best documentation for these can be found in the pkg-config manual pages.



For the purpose of this example, only one macro is used, PKG_CHECK_MODULES, which is used as part of configure.ac for pkg-config integration For the purpose of this example, only one macro is used, <code>PKG_CHECK_MODULES</code>, which is used as part of configure.ac for pkg-config integration



  <tt><span>''<span><font color="#9A1900"><nowiki># Check whether the necessary pkg-config packages are present. The</nowiki></font></span>''</span>   <tt><span>''<span><font color="#9A1900"><nowiki># Check whether the necessary pkg-config packages are present. The</nowiki></font></span>''</span>
Line 1,171:
Line 1,171:
  <span><font color="#009900">LIBS</font></span><span><font color="#990000"><nowiki>=</nowiki></font></span><span><font color="#FF0000">"$HHW_LIBS $LIBS"</font></span></tt>   <span><font color="#009900">LIBS</font></span><span><font color="#990000"><nowiki>=</nowiki></font></span><span><font color="#FF0000">"$HHW_LIBS $LIBS"</font></span></tt>



The proper placing for this code is after all the AC_PROG_* checks and before the AC_OUTPUT macros (so that the build flags may affect the substituted files). The proper placing for this code is after all the <code>AC_PROG_*</code> checks and before the <code>AC_OUTPUT</code> macros (so that the build flags may affect the substituted files).



Check also the validity of the package names by using: Check also the validity of the package names by using:



imported_>amigadave: /* Cleaning up */ use 
2010-07-19T14:30:15Z
Cleaning up:  use <source>

				
				
				
				
				
				← Older revision
				Revision as of 14:30, 19 July 2010
				
Line 1,121:
Line 1,121:
The contents of antigen.sh that is suitable for simple projects: autoconf-automake/example3/antigen.sh The contents of antigen.sh that is suitable for simple projects: autoconf-automake/example3/antigen.sh



 <tt><span>''<span><font color="#9A1900"><nowiki>#!/bin/sh</nowiki></font></span>''</span> <source lang="bash">
 <span>''<span><font color="#9A1900"><nowiki>#</nowiki></font></span>''</span> #!/bin/sh
 <span>''<span><font color="#9A1900"><nowiki># A utility script to remove all generated files.</nowiki></font></span>''</span> #
 <span>''<span><font color="#9A1900"><nowiki>#</nowiki></font></span>''</span> # A utility script to remove all generated files.
 <span>''<span><font color="#9A1900"><nowiki># Running autogen.sh will be required after running this script since</nowiki></font></span>''</span> #
 <span>''<span><font color="#9A1900"><nowiki># the 'configure' script will also be removed.</nowiki></font></span>''</span> # Running autogen.sh will be required after running this script since
 <span>''<span><font color="#9A1900"><nowiki>#</nowiki></font></span>''</span> # the 'configure' script will also be removed.
 <span>''<span><font color="#9A1900"><nowiki># This script is mainly useful when testing autoconf/automake changes</nowiki></font></span>''</span> #
 <span>''<span><font color="#9A1900"><nowiki># and as a part of their development process.</nowiki></font></span>''</span> # This script is mainly useful when testing autoconf/automake changes
 <span>''<span><font color="#9A1900"><nowiki># If there's a Makefile, then run the 'distclean' target first (which</nowiki></font></span>''</span> # and as a part of their development process.
 <span>''<span><font color="#9A1900"><nowiki># will also remove the Makefile).</nowiki></font></span>''</span> # If there's a Makefile, then run the 'distclean' target first (which
 <span>'''<span><font color="#0000FF">if</font></span>'''</span> <span>'''<span><font color="#0000FF">test</font></span>'''</span> -f Makefile<span><font color="#990000"><nowiki>;</nowiki></font></span> <span>'''<span><font color="#0000FF">then</font></span>'''</span> # will also remove the Makefile).
   make distclean if test -f Makefile; then
 <span>'''<span><font color="#0000FF">fi</font></span>'''</span>   make distclean
 <span>''<span><font color="#9A1900"><nowiki># Remove all tar-files (assuming there are some packages).</nowiki></font></span>''</span> fi
 rm -f <span><font color="#990000"><nowiki>*.</nowiki></font></span>tar<span><font color="#990000">.*</font></span> <span><font color="#990000"><nowiki>*.</nowiki></font></span>tgz # Remove all tar-files (assuming there are some packages).
 <span>''<span><font color="#9A1900"><nowiki># Also remove the autotools cache directory.</nowiki></font></span>''</span> rm -f *.tar.* *.tgz
 rm -Rf autom4te<span><font color="#990000">.</font></span>cache # Also remove the autotools cache directory.
 <span>''<span><font color="#9A1900"><nowiki># Remove rest of the generated files.</nowiki></font></span>''</span> rm -Rf autom4te.cache
 rm -f Makefile<span><font color="#990000">.</font></span><span>'''<span><font color="#0000FF">in</font></span>'''</span> aclocal<span><font color="#990000">.</font></span>m4 configure depcomp install-sh missing # Remove rest of the generated files.
 </tt> rm -f Makefile.in aclocal.m4 configure depcomp install-sh missing
</source>



=== Integration with Pkg-Config === === Integration with Pkg-Config ===



imported_>amigadave: /* Introducing Automake */ use 
2010-07-19T14:21:51Z
Introducing Automake:  use <source>
Show changes


imported_>amigadave: /* Substitutions */ use ,  and 

2010-07-19T13:59:08Z
Substitutions:  use <source>, <pre> and <code>
Show changes


imported_>amigadave: /* GNU Autoconf */ use  and 

2010-07-19T13:53:47Z
GNU Autoconf:  use <source> and <code>
Show changes


imported_>amigadave: /* Recursive Variables */ use 
2010-07-19T13:47:32Z
Recursive Variables:  use <source>

				
				
				
				
				
				← Older revision
				Revision as of 13:47, 19 July 2010
				
Line 396:
Line 396:
Now the previously used makefile is reused, but some variables are introduced. This also shows the syntax of defining the variables, and how to use them (reference them): simple-make-files/Makefile.5 Now the previously used makefile is reused, but some variables are introduced. This also shows the syntax of defining the variables, and how to use them (reference them): simple-make-files/Makefile.5



 <tt><span>''<span><font color="#9A1900"><nowiki># define the command that we use for compilation</nowiki></font></span>''</span> <source lang="make">
 CC <span><font color="#990000"><nowiki>=</nowiki></font></span> gcc -Wall # define the command that we use for compilation
 <span>''<span><font color="#9A1900"><nowiki># which targets do we want to build by default?</nowiki></font></span>''</span> CC = gcc -Wall
 <span>''<span><font color="#9A1900"><nowiki># note that 'targets' is just a variable, its name</nowiki></font></span>''</span> # which targets do we want to build by default?
 <span>''<span><font color="#9A1900"><nowiki># does not have any special meaning to make</nowiki></font></span>''</span> # note that 'targets' is just a variable, its name
 targets <span><font color="#990000"><nowiki>=</nowiki></font></span> hello # does not have any special meaning to make
 <span>''<span><font color="#9A1900"><nowiki># first target defined will be the default target</nowiki></font></span>''</span> targets = hello
 <span>''<span><font color="#9A1900"><nowiki># we use the variable to hold the dependencies</nowiki></font></span>''</span> # first target defined will be the default target
 <span><font color="#990000">.</font></span>PHONY<span><font color="#990000"><nowiki>:</nowiki></font></span> all # we use the variable to hold the dependencies
 all<span><font color="#990000"><nowiki>:</nowiki></font></span> <span><font color="#009900">$(targets)</font></span> .PHONY: all
 hello<span><font color="#990000"><nowiki>:</nowiki></font></span> hello<span><font color="#990000">.</font></span>o hello_func<span><font color="#990000">.</font></span>o all: $(targets)
         <span><font color="#009900">$(CC)</font></span> hello<span><font color="#990000">.</font></span>o hello_func<span><font color="#990000">.</font></span>o -o hello hello: hello.o hello_func.o
 hello<span><font color="#990000">.</font></span>o<span><font color="#990000"><nowiki>:</nowiki></font></span> hello<span><font color="#990000">.</font></span>c hello_api<span><font color="#990000">.</font></span>h         $(CC) hello.o hello_func.o -o hello
         <span><font color="#009900">$(CC)</font></span> -c hello<span><font color="#990000">.</font></span>c -o hello<span><font color="#990000">.</font></span>o hello.o: hello.c hello_api.h
 hello_func<span><font color="#990000">.</font></span>o<span><font color="#990000"><nowiki>:</nowiki></font></span> hello_func<span><font color="#990000">.</font></span>c hello_api<span><font color="#990000">.</font></span>h         $(CC) -c hello.c -o hello.o
         <span><font color="#009900">$(CC)</font></span> -c hello_func<span><font color="#990000">.</font></span>c -o hello_func<span><font color="#990000">.</font></span>o hello_func.o: hello_func.c hello_api.h
 <span>''<span><font color="#9A1900"><nowiki># we'll make our cleaning target more powerful</nowiki></font></span>''</span>         $(CC) -c hello_func.c -o hello_func.o
 <span>''<span><font color="#9A1900"><nowiki># we remove the targets that we build by default and also</nowiki></font></span>''</span> # we'll make our cleaning target more powerful
 <span>''<span><font color="#9A1900"><nowiki># remove all object files</nowiki></font></span>''</span> # we remove the targets that we build by default and also
 <span><font color="#990000">.</font></span>PHONY<span><font color="#990000"><nowiki>:</nowiki></font></span> clean # remove all object files
 clean<span><font color="#990000"><nowiki>:</nowiki></font></span> .PHONY: clean
         rm -f <span><font color="#009900">$(targets)</font></span> <span><font color="#990000"><nowiki>*.</nowiki></font></span>o clean:
 </tt>         rm -f $(targets) *.o
</source>



The CC variable is the standard variable to hold the name of the C compiler executable. GNU make comes preloaded with a list of tools that can be accessed in similar way (as will be shown with $(RM) shortly, but there are others). Most UNIX tools related to building software already have similar pre-defined variables in GNU make. Here one of them is overridden to demonstrate how it is done. Overriding variables like this is not recommended, because the user running make later might want to use some other compiler, and would have to edit the makefile to do so. The CC variable is the standard variable to hold the name of the C compiler executable. GNU make comes preloaded with a list of tools that can be accessed in similar way (as will be shown with $(RM) shortly, but there are others). Most UNIX tools related to building software already have similar pre-defined variables in GNU make. Here one of them is overridden to demonstrate how it is done. Overriding variables like this is not recommended, because the user running make later might want to use some other compiler, and would have to edit the makefile to do so.

← Older revision		Revision as of 15:04, 7 September 2010
Line 1,150:		Line 1,150:
	Pkg-config comes with a macro package ('''pkg.m4'''), which contains some useful macros for integration. The best documentation for these can be found in the pkg-config manual pages.		Pkg-config comes with a macro package ('''pkg.m4'''), which contains some useful macros for integration. The best documentation for these can be found in the pkg-config manual pages.

	For the purpose of this example, only one macro is used, PKG_CHECK_MODULES, which is used as part of configure.ac for pkg-config integration		For the purpose of this example, only one macro is used, <code>PKG_CHECK_MODULES</code>, which is used as part of configure.ac for pkg-config integration

	<tt><span>''<span><font color="#9A1900"><nowiki># Check whether the necessary pkg-config packages are present. The</nowiki></font></span>''</span>		<tt><span>''<span><font color="#9A1900"><nowiki># Check whether the necessary pkg-config packages are present. The</nowiki></font></span>''</span>
Line 1,171:		Line 1,171:
	<span><font color="#009900">LIBS</font></span><span><font color="#990000"><nowiki>=</nowiki></font></span><span><font color="#FF0000">"$HHW_LIBS $LIBS"</font></span></tt>		<span><font color="#009900">LIBS</font></span><span><font color="#990000"><nowiki>=</nowiki></font></span><span><font color="#FF0000">"$HHW_LIBS $LIBS"</font></span></tt>

	The proper placing for this code is after all the AC_PROG_* checks and before the AC_OUTPUT macros (so that the build flags may affect the substituted files).		The proper placing for this code is after all the <code>AC_PROG_*</code> checks and before the <code>AC_OUTPUT</code> macros (so that the build flags may affect the substituted files).

	Check also the validity of the package names by using:		Check also the validity of the package names by using:

← Older revision		Revision as of 14:30, 19 July 2010
Line 1,121:		Line 1,121:
	The contents of antigen.sh that is suitable for simple projects: autoconf-automake/example3/antigen.sh		The contents of antigen.sh that is suitable for simple projects: autoconf-automake/example3/antigen.sh

	<~~tt><span>''<span><font color~~="~~#9A1900~~">~~<nowiki>~~#!/bin/sh~~</nowiki></font></span>''</span>~~		<source lang="bash">
	~~<span>''<span><font color="~~#~~9A1900"><nowiki>#</nowiki></font></span>''</span>~~		#!/bin/sh
	~~<span>''<span><font color="#9A1900"><nowiki>~~# A utility script to remove all generated files.~~</nowiki></font></span>''</span>~~		#
	~~<span>''<span><font color="#9A1900"><nowiki>~~#~~</nowiki></font></span>''</span>~~		# A utility script to remove all generated files.
	~~<span>''<span><font color="#9A1900"><nowiki>~~# Running autogen.sh will be required after running this script since~~</nowiki></font></span>''</span>~~		#
	~~<span>''<span><font color="#9A1900"><nowiki>~~# the 'configure' script will also be removed.~~</nowiki></font></span>''</span>~~		# Running autogen.sh will be required after running this script since
	~~<span>''<span><font color="#9A1900"><nowiki>~~#~~</nowiki></font></span>''</span>~~		# the 'configure' script will also be removed.
	~~<span>''<span><font color="#9A1900"><nowiki>~~# This script is mainly useful when testing autoconf/automake changes~~</nowiki></font></span>''</span>~~		#
	~~<span>''<span><font color="#9A1900"><nowiki>~~# and as a part of their development process.~~</nowiki></font></span>''</span>~~		# This script is mainly useful when testing autoconf/automake changes
	~~<span>''<span><font color="#9A1900"><nowiki>~~# If there's a Makefile, then run the 'distclean' target first (which~~</nowiki></font></span>''</span>~~		# and as a part of their development process.
	~~<span>''<span><font color="#9A1900"><nowiki>~~# will also remove the Makefile).~~</nowiki></font></span>''</span>~~		# If there's a Makefile, then run the 'distclean' target first (which
	~~<span>'''<span><font color="#0000FF">~~if~~</font></span>'''</span> <span>'''<span><font color="#0000FF">~~test~~</font></span>'''</span>~~ -f Makefile~~<span><font color="#990000"><nowiki>~~;~~</nowiki></font></span> <span>'''<span><font color="#0000FF">~~then~~</font></span>'''</span>~~		# will also remove the Makefile).
	make distclean		if test -f Makefile; then
	~~<span>'''<span><font color="#0000FF">~~fi~~</font></span>'''</span>~~		make distclean
	~~<span>''<span><font color="#9A1900"><nowiki>~~# Remove all tar-files (assuming there are some packages).~~</nowiki></font></span>''</span>~~		fi
	rm -f ~~<span><font color="#990000"><nowiki>~~.~~</nowiki></font></span>~~tar~~<span><font color="#990000">~~.~~</font></span> <span><font color="#990000"><nowiki>~~*.~~</nowiki></font></span>~~tgz		# Remove all tar-files (assuming there are some packages).
	~~<span>''<span><font color="#9A1900"><nowiki>~~# Also remove the autotools cache directory.~~</nowiki></font></span>''</span>~~		rm -f .tar. *.tgz
	rm -Rf autom4te~~<span><font color="#990000">~~.~~</font></span>~~cache		# Also remove the autotools cache directory.
	~~<span>''<span><font color="#9A1900"><nowiki>~~# Remove rest of the generated files.~~</nowiki></font></span>''</span>~~		rm -Rf autom4te.cache
	rm -f Makefile~~<span><font color="#990000">~~.~~</font></span><span>'''<span><font color="#0000FF">~~in~~</font></span>'''</span>~~ aclocal~~<span><font color="#990000">~~.~~</font></span>~~m4 configure depcomp install-sh missing		# Remove rest of the generated files.
	</tt>		rm -f Makefile.in aclocal.m4 configure depcomp install-sh missing
			</source>

	=== Integration with Pkg-Config ===		=== Integration with Pkg-Config ===

← Older revision		Revision as of 13:47, 19 July 2010
Line 396:		Line 396:
	Now the previously used makefile is reused, but some variables are introduced. This also shows the syntax of defining the variables, and how to use them (reference them): simple-make-files/Makefile.5		Now the previously used makefile is reused, but some variables are introduced. This also shows the syntax of defining the variables, and how to use them (reference them): simple-make-files/Makefile.5

	<~~tt><span>''<span><font color~~="~~#9A1900~~">~~<nowiki>~~# define the command that we use for compilation~~</nowiki></font></span>''</span>~~		<source lang="make">
	CC ~~<span><font color~~=~~"#990000"><nowiki>=</nowiki></font></span>~~ gcc -Wall		# define the command that we use for compilation
	~~<span>''<span><font color="#9A1900"><nowiki>~~# which targets do we want to build by default?~~</nowiki></font></span>''</span>~~		CC = gcc -Wall
	~~<span>''<span><font color="#9A1900"><nowiki>~~# note that 'targets' is just a variable, its name~~</nowiki></font></span>''</span>~~		# which targets do we want to build by default?
	~~<span>''<span><font color="#9A1900"><nowiki>~~# does not have any special meaning to make~~</nowiki></font></span>''</span>~~		# note that 'targets' is just a variable, its name
	targets ~~<span><font color="#990000"><nowiki>~~=~~</nowiki></font></span>~~ hello		# does not have any special meaning to make
	~~<span>''<span><font color="#9A1900"><nowiki>~~# first target defined will be the default target~~</nowiki></font></span>''</span>~~		targets = hello
	~~<span>''<span><font color="#9A1900"><nowiki>~~# we use the variable to hold the dependencies~~</nowiki></font></span>''</span>~~		# first target defined will be the default target
	~~<span><font color="#990000">~~.~~</font></span>~~PHONY~~<span><font color="#990000"><nowiki>~~:~~</nowiki></font></span>~~ all		# we use the variable to hold the dependencies
	all~~<span><font color="#990000"><nowiki>~~:~~</nowiki></font></span> <span><font color="#009900">~~$(targets)~~</font></span>~~		.PHONY: all
	hello~~<span><font color="#990000"><nowiki>~~:~~</nowiki></font></span>~~ hello~~<span><font color="#990000">~~.~~</font></span>~~o hello_func~~<span><font color="#990000">~~.~~</font></span>~~o		all: $(targets)
	~~<span><font color="#009900">~~$(CC)~~</font></span>~~ hello~~<span><font color="#990000">~~.~~</font></span>~~o hello_func~~<span><font color="#990000">~~.~~</font></span>~~o -o hello		hello: hello.o hello_func.o
	hello~~<span><font color="#990000">~~.~~</font></span>~~o~~<span><font color="#990000"><nowiki>~~:~~</nowiki></font></span>~~ hello~~<span><font color="#990000">~~.~~</font></span>~~c hello_api~~<span><font color="#990000">~~.~~</font></span>~~h		$(CC) hello.o hello_func.o -o hello
	~~<span><font color="#009900">~~$(CC)~~</font></span>~~ -c hello~~<span><font color="#990000">~~.~~</font></span>~~c -o hello~~<span><font color="#990000">~~.~~</font></span>~~o		hello.o: hello.c hello_api.h
	hello_func~~<span><font color="#990000">~~.~~</font></span>~~o~~<span><font color="#990000"><nowiki>~~:~~</nowiki></font></span>~~ hello_func~~<span><font color="#990000">~~.~~</font></span>~~c hello_api~~<span><font color="#990000">~~.~~</font></span>~~h		$(CC) -c hello.c -o hello.o
	~~<span><font color="#009900">~~$(CC)~~</font></span>~~ -c hello_func~~<span><font color="#990000">~~.~~</font></span>~~c -o hello_func~~<span><font color="#990000">~~.~~</font></span>~~o		hello_func.o: hello_func.c hello_api.h
	~~<span>''<span><font color="#9A1900"><nowiki>~~# we'll make our cleaning target more powerful~~</nowiki></font></span>''</span>~~		$(CC) -c hello_func.c -o hello_func.o
	~~<span>''<span><font color="#9A1900"><nowiki>~~# we remove the targets that we build by default and also~~</nowiki></font></span>''</span>~~		# we'll make our cleaning target more powerful
	~~<span>''<span><font color="#9A1900"><nowiki>~~# remove all object files~~</nowiki></font></span>''</span>~~		# we remove the targets that we build by default and also
	~~<span><font color="#990000">~~.~~</font></span>~~PHONY~~<span><font color="#990000"><nowiki>~~:~~</nowiki></font></span>~~ clean		# remove all object files
	clean~~<span><font color="#990000"><nowiki>~~:~~</nowiki></font></span>~~		.PHONY: clean
	rm -f ~~<span><font color="#009900">~~$(targets)~~</font></span> <span><font color="#990000"><nowiki>~~*.~~</nowiki></font></span>~~o		clean:
	</tt>		rm -f $(targets) *.o
			</source>

	The CC variable is the standard variable to hold the name of the C compiler executable. GNU make comes preloaded with a list of tools that can be accessed in similar way (as will be shown with $(RM) shortly, but there are others). Most UNIX tools related to building software already have similar pre-defined variables in GNU make. Here one of them is overridden to demonstrate how it is done. Overriding variables like this is not recommended, because the user running make later might want to use some other compiler, and would have to edit the makefile to do so.		The CC variable is the standard variable to hold the name of the C compiler executable. GNU make comes preloaded with a list of tools that can be accessed in similar way (as will be shown with $(RM) shortly, but there are others). Most UNIX tools related to building software already have similar pre-defined variables in GNU make. Here one of them is overridden to demonstrate how it is done. Overriding variables like this is not recommended, because the user running make later might want to use some other compiler, and would have to edit the makefile to do so.

Documentation/Maemo 5 Developer Guide/GNU Build System - Revision history

imported_>sicelo at 18:23, 13 October 2014

imported_>dukenukem at 18:58, 20 September 2012

imported_>amigadave: /* Checking for Distribution Sanity */ add link

imported_>amigadave: use and , wikify slightly, add links to examples

imported_>amigadave: use

imported_>amigadave: /* Cleaning up */ use

imported_>amigadave: /* Introducing Automake */ use

imported_>amigadave: /* Substitutions */ use , and

imported_>amigadave: /* GNU Autoconf */ use and

imported_>amigadave: /* Recursive Variables */ use

imported_>amigadave: use and `, wikify slightly, add links to examples`

imported_>amigadave: /* Substitutions */ use ,
and