{"id":398,"date":"2019-04-30T03:36:34","date_gmt":"2019-04-30T03:36:34","guid":{"rendered":"http:\/\/kabiliravi.com\/?page_id=398"},"modified":"2019-07-21T13:47:54","modified_gmt":"2019-07-21T13:47:54","slug":"build-and-run-your-first-application-with-make","status":"publish","type":"page","link":"http:\/\/kabiliravi.com\/index.php\/software\/programming\/mycpptutorial\/environment-setup\/build-and-run-your-first-application-with-make\/","title":{"rendered":"Build and run your first application with make"},"content":{"rendered":"\n

In this example, we have the same code that we have in Build and run your first application with g++<\/a> but here we use make<\/strong> and Makefile<\/strong> to compile and link the source code.<\/p>\n\n\n\n

You can find the source code of this sample here in Github<\/a>.<\/p>\n\n\n\n

The same as previous example, the application contains three files: hello.h<\/strong>, hello.cpp<\/strong> and main.cpp<\/strong>.<\/p>\n\n\n\n

In order to use make<\/strong> for compilation, the first step is create a file in the root of your project called Makefile<\/strong><\/p>\n\n\n\n

In short, a Makefile has a general syntax called Rule Syntax:<\/p>\n\n\n\n

targets : prerequisites\n        recipe\n...\n<\/pre>\n\n\n\n
target(s)<\/strong> is\/are the generated or resulted files that the recipe<\/strong> section generates and the recipe<\/strong> can have prerequisites<\/strong> <\/p>\n\n\n\n
Here is a simple example is you want to compile and link hello.h<\/strong>, hello.cpp<\/strong> and main.cpp<\/strong><\/p>\n\n\n\nMakefile<\/b>\n
\nCC=g++\nDEPS = hello.h\nOBJ = hello.o main.o\n\n%.o: %.cpp $(DEPS)\n\t$(CC) -c -o $@ $<\n\ngreet: $(OBJ)\n\t$(CC) -o $@ $^\n<\/pre>\n\n\n\n
Save above content is a file called Makefile<\/strong> in the root folder of your project. I go to the Makefile line by line. <\/p>\n\n\n\n
The first line is CC=g++<\/strong>. I defined CC<\/strong> variable to indicate the compiler which g++<\/strong> in here  to compile C++ files.  <\/p>\n\n\n\n
In the second line, I defined DEPS<\/strong> variable to list all header (.h) files which are needed to compile implementation (.cpp) files. Since we have only one header file DEPS = hello.h<\/strong><\/p>\n\n\n\n
In the third line, I listed the object compiled file which are result of the compilation of each .cpp file as a variable named OBJ<\/strong>. We have two .cpp files, one is hello.cpp that has the implementation of hello() function and main.cpp that is the consumer of hell() function in the main() method which is the starting point of the application. 
So OBJ = hello.o main.o<\/strong><\/p>\n\n\n\n
Next is a two line paragraph, we call it Rule<\/strong> in Makefile. The target is %.o<\/strong> which means any file name with .o extension. In the prerequisites<\/strong> section I defined %.cpp $(DEPS)<\/strong> which means all .cpp files (hello.cpp and main.cpp) and DEPS variable has hello.h in it. In the recipe<\/strong> section $(CC)<\/strong> points to the value of CC variable which is g++ and -c<\/strong> means \"Only run preprocess, compile, and assemble steps\".<\/em>  -o<\/strong> is a switch to indicate the name of the output object file which refers to $@<\/strong> and $@ means the target which is %.o<\/strong>. And finally $< means just the first prerequisite that equals to %.cpp<\/strong> that we defined in prerequisite section.<\/p>\n\n\n\n
The last rule creates executable file that I named it greet<\/strong>. The target name is greet:<\/strong>. Prerequisite is $(OBJ)<\/strong> that has hello.o main.o values and in the recipe section we link all object files into one executable file called greet<\/em>. $(CC) is the compiler, -o indicates output file, greet in this case that using $@<\/strong> you refer to target name in the rule you define and $^ list all prerequisite items<\/p>\n\n\n\n
The value of '$^<\/strong>' is a list of all the prerequisites of the rule, including the names of the directories in which they were found, and the value of '$@'<\/strong> is the target<\/p><\/blockquote>\n\n\n\n
Now in a terminal run make<\/strong> to execute Makefile that you created.<\/p>\n\n\n\n
$ make\ng++ -c -o hello.o hello.cpp\ng++ -c -o main.o main.cpp\ng++ -o greet hello.o main.o\n<\/pre>\n\n\n\n
And finally run your app:<\/p>\n\n\n\n
$ .\/greet\nHello World!\n<\/pre>\n","protected":false},"excerpt":{"rendered":"
In this example, we have the same code that we have in Build and run your first application with g++ but here we use make and Makefile to compile and link the source code. You can find the source code of this sample here in Github. The same as previous example, the application contains three […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":274,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"ngg_post_thumbnail":0,"footnotes":""},"class_list":["post-398","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/pages\/398","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/comments?post=398"}],"version-history":[{"count":10,"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/pages\/398\/revisions"}],"predecessor-version":[{"id":451,"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/pages\/398\/revisions\/451"}],"up":[{"embeddable":true,"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/pages\/274"}],"wp:attachment":[{"href":"http:\/\/kabiliravi.com\/index.php\/wp-json\/wp\/v2\/media?parent=398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}