Writing Make Files - Revision history

Jadrian Miles: Small explanation about how to use make once you've written a Makefile

2013-01-17T23:18:08Z

Small explanation about how to use make once you've written a Makefile

← Older revision		Revision as of 23:18, 17 January 2013
Line 1:		Line 1:
	The VRL has a custom system of support code for writing cross-platform, multi-compiler-version Makefiles. This helps tame the otherwise brutal strength of the [http://www.gnu.org/software/make/manual/make.html GNU Make], in which it's really easy to write unmaintainable code and shoot oneself in the foot. A Makefile that uses the G Build system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.		The VRL has a custom system of support code for writing cross-platform, multi-compiler-version Makefiles. This helps tame the otherwise brutal strength of the [http://www.gnu.org/software/make/manual/make.html GNU Make], in which it's really easy to write unmaintainable code and shoot oneself in the foot. A Makefile that uses the G Build system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.

	Once you've written a Makefile in your directory, you call the command <tt>make</tt> ~~to build~~ the ~~program~~ according to the instructions implicit in the Makefile.		Once you've written a Makefile in your directory, you call the command <code>make</code> to build your program. The <tt>make</tt> program runs other commands (like invoking the compiler or linker) in order, according to the instructions implicit in the Makefile.

	Below is a fairly exhaustive listing of all the Make variables that you can put in your custom Makefile in order to control your build. But first you should check out the sample Makefiles for a simple '''[[Example Makefile for a program\|program]]''' and '''[[Example Makefile for a library\|library]]'''.		Below is a fairly exhaustive listing of all the Make variables that you can put in your custom Makefile in order to control your build. But first you should check out the sample Makefiles for a simple '''[[Example Makefile for a program\|program]]''' and '''[[Example Makefile for a library\|library]]'''.

Jadrian Miles at 23:16, 17 January 2013

2013-01-17T23:16:23Z

← Older revision		Revision as of 23:16, 17 January 2013
Line 1:		Line 1:
	The VRL has a custom system of support code for writing cross-platform, multi-compiler-version Makefiles. This helps tame the otherwise brutal strength of the [http://www.gnu.org/software/make/manual/make.html GNU Make], in which it's really easy to write unmaintainable code and shoot oneself in the foot. A Makefile that uses the G Build system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.		The VRL has a custom system of support code for writing cross-platform, multi-compiler-version Makefiles. This helps tame the otherwise brutal strength of the [http://www.gnu.org/software/make/manual/make.html GNU Make], in which it's really easy to write unmaintainable code and shoot oneself in the foot. A Makefile that uses the G Build system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.

			Once you've written a Makefile in your directory, you call the command <tt>make</tt> to build the program according to the instructions implicit in the Makefile.

	Below is a fairly exhaustive listing of all the Make variables that you can put in your custom Makefile in order to control your build. But first you should check out the sample Makefiles for a simple '''[[Example Makefile for a program\|program]]''' and '''[[Example Makefile for a library\|library]]'''.		Below is a fairly exhaustive listing of all the Make variables that you can put in your custom Makefile in order to control your build. But first you should check out the sample Makefiles for a simple '''[[Example Makefile for a program\|program]]''' and '''[[Example Makefile for a library\|library]]'''.

Jadrian Miles: Cleaned up intro text

2013-01-17T23:14:11Z

Cleaned up intro text

← Older revision		Revision as of 23:14, 17 January 2013
Line 1:		Line 1:
	A Makefile that uses the G Build ~~make~~ system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.		The VRL has a custom system of support code for writing cross-platform, multi-compiler-version Makefiles. This helps tame the otherwise brutal strength of the [http://www.gnu.org/software/make/manual/make.html GNU Make], in which it's really easy to write unmaintainable code and shoot oneself in the foot. A Makefile that uses the G Build system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.

	~~If you are new to~~ Make you ~~will need~~ to ~~familiarize yourself with it before reading this document~~. ~~Make is~~ a ~~fairly user hostile language. The semantics are difficult to learn~~ and ~~error messages tend to be uninformative. However, Make is~~ a ~~language that is hard to avoid so most programmers become familiar with it. The G Build system uses Gnu make as it has consistent behavior over many platforms~~.		Below is a fairly exhaustive listing of all the Make variables that you can put in your custom Makefile in order to control your build. But first you should check out the sample Makefiles for a simple '''[[Example Makefile for a program\|program]]''' and '''[[Example Makefile for a library\|library]]'''.

	http://www.gnu.org/software/make/manual/make.html		Just working from the examples, it's straightforward to get started building your program ''so long as it is located in a standard sandbox directory''. See the [[Software Development\|software development documentation]] for more details. However, if you are new to Make, you may find it useful to familiarize yourself with it. Make is a fairly user hostile language. The semantics are difficult to learn and error messages tend to be uninformative. However, Make is a language that is hard to avoid so most programmers become familiar with it. The G Build system uses Gnu make as it has consistent behavior over many platforms. So when please take the time to [http://www.gnu.org/software/make/manual/make.html read the official documentation] or [http://www.google.com/search?q=gnu+make+tutorial find a good tutorial].


	~~Sample Makefiles for a simple '''[[program]~~]~~''' and '''~~[~~[library]~~]~~'''~~.

Brad Berg: /* Make File Contents */

2011-03-08T18:11:47Z

Make File Contents

← Older revision		Revision as of 18:11, 8 March 2011
Line 33:		Line 33:
	[[BIN_SCRIPT]] += <Script Files> ... Install files in the bin directory.		[[BIN_SCRIPT]] += <Script Files> ... Install files in the bin directory.
	[[SHARE_FILE]] += <Shared Files> ... Install files in the share directory.		[[SHARE_FILE]] += <Shared Files> ... Install files in the share directory.
	[[SHARE_DIRECTORY]] += <Shared Directories> ... Install directories in the share directory.		<!-- [[SHARE_DIRECTORY]] += <Shared Directories> ... Install directories in the share directory. -->
	[[LDLIB]] += <Linker Setting> ... Pass libraries directly to the linker.		[[LDLIB]] += <Linker Setting> ... Pass libraries directly to the linker.
	[[CXXFLAGS]] += <C++ Compiler Flag> ... Pass flags directly to the C++ compiler.		[[CXXFLAGS]] += <C++ Compiler Flag> ... Pass flags directly to the C++ compiler.

Brad Berg at 14:46, 7 March 2011

2011-03-07T14:46:26Z

← Older revision		Revision as of 14:46, 7 March 2011
Line 1:		Line 1:
	A Makefile that uses the G Build make system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.		A Makefile that uses the G Build make system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.

	If you are new to Make you will need to familiarize yourself with it before reading this document. Make is a fairly user hostile language. The error messages tend to be uninformative. However, Make is a language that is hard to avoid so most programmers ~~are~~ familiar with it. The G Build system uses Gnu make as it has consistent behavior over many platforms.		If you are new to Make you will need to familiarize yourself with it before reading this document. Make is a fairly user hostile language. The semantics are difficult to learn and error messages tend to be uninformative. However, Make is a language that is hard to avoid so most programmers become familiar with it. The G Build system uses Gnu make as it has consistent behavior over many platforms.

	http://www.gnu.org/software/make/manual/make.html		http://www.gnu.org/software/make/manual/make.html

Brad Berg at 14:21, 7 March 2011

2011-03-07T14:21:18Z

← Older revision		Revision as of 14:21, 7 March 2011
Line 31:		Line 31:

	* '''Variable Settings For Experts'''		* '''Variable Settings For Experts'''
	[[BIN_SCRIPT]] += <Script Files> ... Install files in the bin directory.		[[BIN_SCRIPT]] += <Script Files> ... Install files in the bin directory.
	[[SHARE_FILE]] += <Shared Files> ... Install files in the share directory.		[[SHARE_FILE]] += <Shared Files> ... Install files in the share directory.
	[[LDLIB]] += <Linker Setting> ... Pass libraries directly to the linker.		[[SHARE_DIRECTORY]] += <Shared Directories> ... Install directories in the share directory.
	[[CXXFLAGS]] += <C++ Compiler Flag> ... Pass flags directly to the C++ compiler.		[[LDLIB]] += <Linker Setting> ... Pass libraries directly to the linker.
	[[CFLAGS]] += <C Compiler Flag> ... Pass flags directly to the C compiler.		[[CXXFLAGS]] += <C++ Compiler Flag> ... Pass flags directly to the C++ compiler.
	[[CXXINC]] += <Include Directory> ... Pass includes directly to the C++ compiler.		[[CFLAGS]] += <C Compiler Flag> ... Pass flags directly to the C compiler.
	[[CINC]] += <Include Directory> ... Pass includes directly to the C compiler.		[[CXXINC]] += <Include Directory> ... Pass includes directly to the C++ compiler.
			[[CINC]] += <Include Directory> ... Pass includes directly to the C compiler.

Brad Berg: New page: A Makefile that uses the G Build make system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in...

2010-11-19T16:30:02Z

New page: A Makefile that uses the G Build make system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in...

New page

A Makefile that uses the G Build make system will build a single directory containing one library and/or one or more programs. Projects can consist of a directory tree with a Make File in each directory.

If you are new to Make you will need to familiarize yourself with it before reading this document. Make is a fairly user hostile language. The error messages tend to be uninformative. However, Make is a language that is hard to avoid so most programmers are familiar with it. The G Build system uses Gnu make as it has consistent behavior over many platforms.

http://www.gnu.org/software/make/manual/make.html

Sample Makefiles for a simple '''[[program]]''' and '''[[library]]'''.

=== '''Make File Contents''' ===

* '''Make Variable Settings'''

[[G_COMPILER]] = <Compiler Version> Designate a compiler and version.
[[PROJECT]] = <Project Name> Required project name.
[[PROJECT_HOME]] = <Root Directory> Subdirectories reference the project root.

[[LIBRARY]] = <Library Name> Use when the directory contains a library.
[[CXXSRC]] = <C++ Source>.cpp ... List C++ source files for a library.
[[CSRC]] = <C Source>.c ... List C source files for a library.
[[INCLUDE_H]] = <C/C++ Header> ... List public library headers to install.

[[PROGRAM]] = <Program Name> ... List each program in the directory.
[[CXX]]<Program> = <C++ Source>.cpp ... List C++ source files for a program.
[[C]]<Program> = <C Source>.c ... List C source files for a program.

[[G_USE]] = <Package Name> ... Predefined settings for packages.
[[LDLIB_VER]] = <Library Name> ... Link a program with a library.
[[LDLIB_PROJECT]] = <Project Name> ... Add a project library to the search path.

* '''Variable Settings For Experts'''
[[BIN_SCRIPT]] += <Script Files> ... Install files in the bin directory.
[[SHARE_FILE]] += <Shared Files> ... Install files in the share directory.
[[LDLIB]] += <Linker Setting> ... Pass libraries directly to the linker.
[[CXXFLAGS]] += <C++ Compiler Flag> ... Pass flags directly to the C++ compiler.
[[CFLAGS]] += <C Compiler Flag> ... Pass flags directly to the C compiler.
[[CXXINC]] += <Include Directory> ... Pass includes directly to the C++ compiler.
[[CINC]] += <Include Directory> ... Pass includes directly to the C compiler.

Always add this include statement to bring in the G Build make files.

<pre>
include $(G)/common/build/make/directory.make
</pre>

Optionally add this include statement to build using all available compilers. Note that when including this make file additional targets are declared for:<br>
:::install all allclean

<pre>
include $(G)/common/build/make/build.multiple.make
</pre>

* '''Directory Access variables'''

These variables can be used to access directories to avoid using hard coded paths. Do not set these variables.

[[G_IMPORT]] Location where third party software is installed.
[[G_INSTALL]] Location where files are installed with "make install".

=== '''Projects With Multiple Directories''' ===

Projects can contain a directory tree that can be organized any way the developers chooses. Make files using the Build system each build a single directory in the tree. By convention the default Make target ("make" with no operand) will build the current directory for a single compiler. By convention an "all" target will build the current directory and all of it's subdirectories.

Usually Makefiles in a directory above several subdirectories will use Gnu Make commands to build the subdirectories. In this case you won't need to include the '''directory.make''' file. Here are some typical Gnu Make commands you might want to use:

<pre>
# Require that the all targets always be used.
#
default:
@echo "Use: make all"

clean:
@echo "Use: make allclean"

test:
@echo "Use: make alltest"
</pre>

<pre>
# Create a target to clean all the subdirectories.
#
allclean:
$(MAKE) -C utility allclean
$(MAKE) -C library allclean
$(MAKE) -C program allclean
</pre>

<pre>
# Create a target to build one subdirectory.
#
.PHONY: utility
utility:
$(MAKE) -C utility all
</pre>

Only a small subset of Unix Utilities is included in the G Build system. Limiting the use of Unix commands in rules makes it easier to get a project developed on Unix to work on native Windows. Complex commands can invoke scripts. Python is recommended as you can use it to easily write platform independent scripts with good error reporting.