Make - Revision history

Christoph at 03:38, 1 October 2009

2009-10-01T03:38:02Z

Christoph at 02:10, 25 August 2007

2007-08-25T02:10:49Z

Christoph at 02:56, 14 June 2007

2007-06-14T02:56:49Z

Christoph at 07:14, 12 February 2007

2007-02-12T07:14:57Z

Christoph: /* PATH */

2006-12-01T00:23:22Z

‎PATH

Christoph at 01:35, 19 October 2006

2006-10-19T01:35:46Z

Christoph at 01:25, 19 October 2006

2006-10-19T01:25:21Z

Christoph at 04:37, 13 October 2006

2006-10-13T04:37:29Z

New page

{{lowercase|title=make}}
In computing, '''make''' is a utility that automates the process of generating ("making") a file (or files). The make is most commonly used to generate an application. For each application, a programmer writes a file named "<code>makefile</code>" or (later) "<code>Makefile</code>", which tells make all the files and other tools involved in generating the final output file (or files).

== Example makefile ==
''Note: A random mix of stuff for examples.''
<pre>
SHELL = /bin/sh

AWK = awk
SED = sed
RM = rm

# Clear out pre-defined suffixes
.SUFFIXES:
.SUFFIXES: .seg .pdb .dat .log

%.seg: %.log
$(SED) -n '/^[0-9]/{n;p;}' $< | \
$(SED) -e 's/ [0-9].*\.$.*$//' >$@

SEG = 01 02 03 04 05

%.seg.s: %.seg
for n in $(SEG);\
do \
head -$$n $< | \
tail -1 | \
$(SED) 's/[)|;]/\n/g' - | \
head -$$n | \
$(SED) 's/[(('$(CH)':)| ]//g' - | \
$(SED) 's/-/\t/g' - | \
sort -nk1 - | \
$(SED) = - | $(SED) 'N;s/\n/\t/' >$@$$n ;\
done

show:
@echo "***************************************"
@echo SED = $(SED)

LIST = one two three
blah:
@for i in $(LIST); do \
echo $$i; \
done

clean:
$(RM) *.seg.s*
</pre>

== Useful utilities ==
=== Core ===
cat cmp cp diff echo egrep expr false grep install-info
ln ls mkdir mv pwd rm rmdir sed sleep sort tar test touch true
=== Extended ===
[ basename bash cat chgrp chmod chown cmp cp dd diff echo
egrep expand expr false fgrep find getopt grep gunzip gzip
hostname install install-info kill ldconfig ln ls md5sum
mkdir mkfifo mknod mv printenv pwd rm rmdir sed sort tee
test touch true uname xargs yes

== External links ==
* [http://www.gnu.org/software/make/manual/html_node/index.html The GNU make manual]
* [[wikipedia:make]]

[[Category:Scripting languages]]

← Older revision		Revision as of 03:38, 1 October 2009
Line 2:		Line 2:

	Most of the article will disuces the '''GNU Make''' (or '''gmake''') version.		Most of the article will disuces the '''GNU Make''' (or '''gmake''') version.
		+
		+	==Introduction==
		+	'''gmake''' is a system which allows one to automate tasks. In many cases, doing something involves several steps, such as converting files, calculating something, and making a graphic file of it all. When using gmake, one specifies what kind of file one wishes to end up with, and the computer figures out what steps need to be done to get to that point. For an example, one could have a [[genbank]] file and would only want the [[fasta]] sequence of the genome. If the file is named "foo.gbk", then one could use gmake to get the fasta sequence: execute "<code>gmake foo.fsa</code>" (i.e., replace the ending with what one wants to end up with).

	==PATH==		==PATH==

@@ Line 1: / Line 1: @@
 In computing, '''make''' is a utility that automates the process of generating ("making") a file (or files). The make is most commonly used to generate an application. For each application, a programmer writes a file named "<code>makefile</code>" or (later) "<code>Makefile</code>", which tells make all the files and other tools involved in generating the final output file (or files).
 ==PATH==
@@ Line 107: / Line 108: @@
 ==External links==
 *[http://www.gnu.org/software/make/manual/html_node/index.html The GNU make manual]
 *[[wikipedia:make]]
 [[Category:Scripting languages]]

@@ Line 2: / Line 2: @@
 In computing, '''make''' is a utility that automates the process of generating ("making") a file (or files). The make is most commonly used to generate an application. For each application, a programmer writes a file named "<code>makefile</code>" or (later) "<code>Makefile</code>", which tells make all the files and other tools involved in generating the final output file (or files).
-== PATH ==
+==PATH==
 You can store all of your personal makefiles in a single directory (e.g. <code>/home/bob/makefiles</code>) and set the environment variable <code>MAKFILES</code> to call these. Note that the make ''file'' itself, with the absolute path must be set in the environment, ''not'' just the path.
@@ Line 13: / Line 13: @@
   include /home/bob/makefiles/foo.mk
-== Functions (built-in) ==
+==Functions (built-in)==
 * Here is a summary of the <tt>gmake</tt> built-in functions (see [http://www.gnu.org/software/make/manual/html_node/Functions.html Functions]):
@@ Line 48: / Line 48: @@
 ; <code>$(value var)</code> : Evaluates to the contents of the variable var, with no expansion performed on it
-== Example makefile ==
+==Example makefile==
 ''Note: A random mix of stuff for examples.''
 <pre>
@@ Line 94: / Line 94: @@
 </pre>
-== Useful utilities ==
+==Useful utilities==
-=== Core ===
+===Core===
   cat cmp cp diff echo egrep expr false grep install-info
   ln ls mkdir mv pwd rm rmdir sed sleep sort tar test touch true
-=== Extended ===
+===Extended===
   [ basename bash cat chgrp chmod chown cmp cp dd diff echo
   egrep expand expr false fgrep find getopt grep gunzip gzip
@@ Line 105: / Line 105: @@
   test touch true uname xargs yes
-== External links ==
+==External links==
-* [http://www.gnu.org/software/make/manual/html_node/index.html The GNU make manual]
+*[http://www.gnu.org/software/make/manual/html_node/index.html The GNU make manual]
-* [[wikipedia:make]]
+*[[wikipedia:make]]
 [[Category:Scripting languages]]

@@ Line 3: / Line 3: @@
 == PATH ==
-You can store all of your personal makefiles in a single directory (e.g. /home/bob/makefiles) and set the environment variable <code>MAKFILES</code> to call these. Note that the make ''file'' itself, with the absolute path must be set in the environment, ''not'' just the path.
+You can store all of your personal makefiles in a single directory (e.g. <code>/home/bob/makefiles</code>) and set the environment variable <code>MAKFILES</code> to call these. Note that the make ''file'' itself, with the absolute path must be set in the environment, ''not'' just the path.
 For an example, in [[bash]] you would add the following to your <code>~/.bashrc</code> file:

@@ Line 12: / Line 12: @@
   include /home/bob/makefiles/Makeconfig
   include /home/bob/makefiles/foo.mk
 == Example makefile ==