Javascript required
Skip to content Skip to sidebar Skip to footer
Home / How to Read Exe File Source Code Mac

How to Read Exe File Source Code Mac

GCC and Make

Compiling, Linking and Building
C/C++ Applications

GCC (GNU Compiler Drove)

A Brief History and Introduction to GCC

The original GNU C Compiler (GCC) is developed by Richard Stallman, the founder of the GNU Projection. Richard Stallman founded the GNU projection in 1984 to create a complete Unix-like operating organisation as gratis software, to promote freedom and cooperation among computer users and programmers.

GCC, formerly for "GNU C Compiler", has grown over times to support many languages such as C (gcc), C++ (1000++), Objective-C, Objective-C++, Java (gcj), Fortran (gfortran), Ada (gnat), Go (gccgo), OpenMP, Cilk Plus, and OpenAcc. Information technology is now referred to every bit "GNU Compiler Collection". The mother site for GCC is http://gcc.gnu.org/. The current version is GCC seven.3, released on 2018-01-25.

GCC is a primal component of so-chosen "GNU Toolchain", for developing applications and writing operating systems. The GNU Toolchain includes:

  1. GNU Compiler Drove (GCC): a compiler suite that supports many languages, such as C/C++ and Objective-C/C++.
  2. GNU Brand: an automation tool for compiling and building applications.
  3. GNU Binutils: a suite of binary utility tools, including linker and assembler.
  4. GNU Debugger (GDB).
  5. GNU Autotools: A build system including Autoconf, Autoheader, Automake and Libtool.
  6. GNU Bison: a parser generator (similar to lex and yacc).

GCC is portable and run in many operating platforms. GCC (and GNU Toolchain) is currently available on all Unixes. They are too ported to Windows (by Cygwin, MinGW and MinGW-W64). GCC is also a cantankerous-compiler, for producing executables on unlike platform.

GCC Versions

The various GCC versions are:

  • GCC version one (1987): Initial version that support C.
  • GCC version two (1992): supports C++.
  • GCC version iii (2001): incorporating ECGS (Experimental GNU Compiler System), with improve optimization.
  • GCC version iv (2005):
  • GCC version five (2015):
  • GCC Version vi (2016):
  • GCC Version 7 (2017):
C++ Standard Support

There are various C++ standards:

  • C++98
  • C++xi (aka C++0x)
  • C++14 (aka C++1y)
  • C++17 (aka C++1z)
  • C++2a (next planned standard in 2020)

The default fashion is C++98 for GCC versions prior to 6.i, and C++14 for GCC 6.1 and to a higher place. You tin utilize command-line flag -std to explicitly specify the C++ standard. For case,

  • -std=c++98, or -std=gnu++98 (C++98 with GNU extensions)
  • -std=c++eleven, or -std=gnu++eleven (C++eleven with GNU extensions)
  • -std=c++14, or -std=gnu++14 (C++14 with GNU extensions), default style for GCC half-dozen.one and higher up.
  • -std=c++17, or -std=gnu++17 (C++17 with GNU extensions), experimental.
  • -std=c++2a, or -std=gnu++2a (C++2a with GNU extensions), experimental.

Installing GCC on Unixes

GNU Toolchain, including GCC, is included in all Unixes. It is the standard compiler for nigh Unix-similar operating systems.

Installing GCC on Mac Os X

Open up a Terminal, and enter "gcc --version". If gcc is non installed, the system will prompt you lot to install gcc.

$          gcc --version          ...... Target: x86_64-apple-darwin14.5.0    Thread model: posix

Installing GCC on Windows

For Windows, you could either install Cygwin GCC, MinGW GCC or MinGW-W64 GCC. Read "How to install Cygwin and MinGW".

  • Cygwin GCC: Cygwin is a Unix-similar environment and command-line interface for Microsoft Windows. Cygwin is huge and includes most of the Unix tools and utilities. It also included the commonly-used Fustigate shell.
  • MinGW: MinGW (Minimalist GNU for Windows) is a port of the GNU Compiler Drove (GCC) and GNU Binutils for use in Windows. It besides included MSYS (Minimal Arrangement), which is basically a Bourne trounce (bash ).
  • MinGW-W64: a fork of MinGW that supports both 32-scrap and 64-bit windows.
Diverse GCCs under Cygwin

At that place are many GCCs nether Cygain/MinGW. To differentiate these variations, you demand to sympathise the followings:

  • Windows/Intel uses these pedagogy sets: x86 is a 32-flake teaching set; i868 is a 32-bit enhanced version of x86; x86_64 (or amd64) is a 64-bit instruction set up.
  • 32-chip compilers/programs tin can run on 32-bit or 64-bit (astern compatible) Windows, but 64-flake compiler tin only run on 64-flake Windows.
  • 64-chip compilers may produce target of 32-bit or 64-bit.
  • If you lot use Cygwin'due south GCC, the target could be native Windows or Cygwin. If the target is native Windows, the code can be distributed and run under Windows. Yet, if the target is Cygwin, to distribute, yous need to distribute Cygwin runtime surroundings (cygwin1.dll). This is because Cygwin is a Unix emulator under Windows.
MinGW-W64 Target 32/64-bit Native Windows

The MinGW-W64 (a fork of MinGW, available at http://mingw-w64.org/doku.php) supports target of both 32-bit and 64-chip native Windows. You can install "MinGW-W64" under "Cygwin" past selecting these packages (under "devel" category):

  • mingw64-x86_64-gcc-core: 64-bit C compiler for target of native 64-bit Windows. The executable is "x86_64-w64-mingw32-gcc".
  • mingw64-x86_64-gcc-g++: 64-bit C++ compiler for target of native 64-chip Windows. The executable is "x86_64-w64-mingw32-g++".
  • mingw64-i686-gcc-core: 64-fleck C compiler for target of native 32-bit Windows. The executable is "i686-w64-mingw32-gcc".
  • mingw64-i686-gcc-g++: 64-chip C++ compiler for target of native 32-bit Windows. The executable is "i686-w64-mingw32-g++".

Notes:

  • I propose you install "mingw64-x86_64-gcc-core" and "mingw64-x86_64-gcc-k++" to provide native 64-bit Windows codes, but skip "mingw64-i686-gcc-core" and "mingw64-i686-gcc-g++", unless yous need to produce 32-bit Windows applications.
  • For JNI (Java Native Interface) in 64-bit Coffee, you lot need to use "x86_64-w64-mingw32-gcc" or "x86_64-w64-mingw32-g++" to produce 64-fleck native Windows lawmaking.

Run the executables and bank check the versions:

            $          x86_64-w64-mingw32-gcc --version          
x86_64-w64-mingw32-gcc (GCC) vi.4.0  $          x86_64-w64-mingw32-gcc -5          
Using built-in specs.
COLLECT_GCC=x86_64-w64-mingw32-gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-w64-mingw32/6.4.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: .....
Thread model: posix
gcc version 6.4.0 (GCC)  $          x86_64-w64-mingw32-g++ --version          
x86_64-w64-mingw32-g++ (GCC) 6.4.0   $          i686-w64-mingw32-gcc --version          
i686-w64-mingw32-gcc (GCC) 6.4.0
          $          i686-w64-mingw32-g++ --version          
i686-w64-mingw32-yard++ (GCC) 6.4.0
Other GCCs in Cygwin

Other GCC packages in Cygwin are:

  • gcc-core, gcc-thou++: Basic 64-bit C/C++ compiler target 64-bit Cygwin. You lot probably should install these ii packages too. All the same, to distribute the code produced, y'all need to distribute Cygwin Runtime Surround (cygwin1.dll). This is because Cygwin is a Unix emulator under Windows.
  • cygwin32-gcc-core, cygwin32-gcc-k++: Older 32-bit C/C++ compiler for target 32-chip Cygwin (Obsoleted by gcc-code and gcc-g++?).
  • mingw-gcc-cadre, mingw-gcc-g++: Older MinGW 32-bit C/C++ compiler for 32-bit Windows (Obsoleted by MinGW-W64 packages?).

Mail Installation

Versions

You could display the version of GCC via --version option:

$          gcc --version          gcc (GCC) vi.4.0  $          k++ --version          g++ (GCC) 6.four.0

More than details can be obtained via -v selection, for example,

$          gcc -v          Using born specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/6.4.0/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: ......
Thread model: posix
gcc version 6.iv.0 (GCC)  $          g++ -5          
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/6.4.0/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: ......
Thread model: posix
gcc version 6.4.0 (GCC)
Help

You can become the help manual via the --help option. For example,

$          gcc --help
Man Pages

You tin can read the GCC manual pages (or man pages) via the man utility:

$          man gcc           $          man thou++

Reading man pages nether CMD or Fustigate beat out tin be hard. You could generate a text file via:

$          homo gcc | col -b > gcc.txt

The col utility is needed to strip the backspace. (For Cygwin, information technology is available in "Utils", "util-linux" package.)

Alternatively, you could look for an online homo pages, due east.m., http://linux.die.internet/homo/1/gcc.

The GCC human pages are kept under "usr/share/man/man1".

$          whereis gcc          gcc: /usr/bin/gcc.exe /usr/lib/gcc /usr/share/homo/man1/gcc.1.gz

Getting Started

The GNU C and C++ compiler are chosen gcc and chiliad++, respectively.

Compile/Link a Simple C Program - hi.c

Below is the Hello-world C program how-do-you-do.c:

1 2 three four 5 6 vii
 
                    #include <stdio.h>   int main() {     printf("Hello, earth!\northward");     render 0; }

To compile the hello.c:

>          gcc hullo.c

The default output executable is called "a.exe" (Windows) or "a.out" (Unixes and Mac Bone X).

To run the programme:

            >          a           $          chmod a+x a.out          $          ./a.out

Notes for Unixes and Bash Vanquish:

  • In Fustigate beat out, the default PATH does not include the current working directory. Hence, yous demand to include the electric current path (./) in the command. (Windows include the current directory in the PATH automatically; whereas Unixes do not - you lot demand to include the current directory explicitly in the PATH.)
  • You also demand to include the file extension, if any, i.e., "./a.out".
  • In Unixes, the output file could be "a.out" or simply "a". Furthermore, you demand to assign executable file-mode (x) to the executable file "a.out", via command "chmod a+x filename " (add executable file-way "+ten" to all users "a+x").

To specify the output filename, use -o choice:

            >          gcc -o hello.exe hello.c           >          hello             $          gcc -o hullo hello.c          $          chmod a+x hullo          $          ./hi

NOTE for Unixes:

  • In Unixes, nosotros typically omit the .exe file extension (meant for Windows but), and simply name the output executable as hello (via command "gcc -o hello hello.c".
  • You need to assign executable file mode via control "chmod a+ten hello".
Compile/Link a Simple C++ Program - howdy.cpp 
1 2 iii 4 5 half-dozen seven 8
 
#include <iostream> using namespace std;   int main() {    cout << "How-do-you-do, world!" << endl;    return 0; }

Y'all need to employ g++ to compile C++ plan, as follows. We utilise the -o option to specify the output file name.

            >          thousand++ -o hullo.exe hello.cpp           >          hi             $          g++ -o hello hello.cpp          $          chmod a+x hello          $          ./hi
More than GCC Compiler Options

A few normally-used GCC compiler options are:

$ g++          -Wall -g -o Hello.exe          Hello.cpp
  • -o: specifies the output executable filename.
  • -Wall: prints "all" Warning letters.
  • -g: generates additional symbolic debugthousandging information for use with gdb debugger.
Compile and Link Separately

The higher up command compile the source file into object file and link with other object files and organisation libraries into executable in one step. Y'all may carve up compile and link in ii steps every bit follows:

            >          g++ -c -Wall -k Hullo.cpp           >          g++ -g -o Hello.exe Hi.o

The options are:

  • -c: Compile into object file "Hello.o". By default, the object file has the aforementioned proper name equally the source file with extension of ".o" (there is no need to specify -o selection). No linking with other object files or libraries.
  • Linking is performed when the input file are object files ".o" (instead of source file ".cpp" or ".c"). GCC uses a separate linker program (called ld.exe) to perform the linking.
Compile and Link Multiple Source Files

Suppose that your program has 2 source files: file1.cpp, file2.cpp. You could compile all of them in a single control:

> g++ -o myprog.exe file1.cpp file2.cpp

However, nosotros usually compile each of the source files separately into object file, and link them together in the later stage. In this example, changes in one file does not require re-compilation of the other files.

>          1000++ -c file1.cpp          >          g++ -c file2.cpp          >          g++ -o myprog.exe file1.o file2.o
Compile into a Shared Library

To compile and link C/C++ program into a shared library (".dll" in Windows, ".so" in Unixes), employ -shared pick. Read "Coffee Native Interface" for example.

GCC Compilation Process

GCC compiles a C/C++ program into executable in 4 steps as shown in the in a higher place diagram. For case, a "gcc -o hello.exe how-do-you-do.c" is carried out as follows:

  1. Pre-processing: via the GNU C Preprocessor (cpp.exe), which includes the headers (#include) and expands the macros (#ascertain). 
    >              cpp hello.c > hello.i
    The resultant intermediate file "hullo.i" contains the expanded source code.
  2. Compilation: The compiler compiles the pre-processed source code into associates code for a specific processor. 
    >              gcc -S how-do-you-do.i
    The -Due south option specifies to produce assembly code, instead of object code. The resultant associates file is "hello.s".
  3. Assembly: The assembler (as.exe) converts the assembly code into car code in the object file "hello.o". 
    >              as -o hullo.o hello.s
  4. Linker: Finally, the linker (ld.exe) links the object lawmaking with the library code to produce an executable file "how-do-you-do.exe". 
    >              ld -o hi.exe hi.o ...libraries...
Verbose Mode (-five)

Y'all tin can come across the detailed compilation process by enabling -v (verbose) choice. For example,

>          gcc -5 -o hello.exe hi.c
Defining Macro (-D)

Yous can use the -Dproper name option to define a macro, or -Dname=value to define a macro with a value. The value should be enclosed in double quotes if it contains spaces.

Headers (.h), Static Libraries (.lib, .a) and Shared Library (.dll, .then)

Static Library vs. Shared Library

A library is a drove of pre-compiled object files that can exist linked into your programs via the linker. Examples are the arrangement functions such equally printf() and sqrt().

At that place are two types of external libraries: static library and shared library.

  1. A static library has file extension of ".a" (archive file) in Unixes or ".lib" (library) in Windows. When your program is linked against a static library, the machine lawmaking of external functions used in your programme is copied into the executable. A static library tin be created via the annal program "ar.exe".
  2. A shared library has file extension of ".and so" (shared objects) in Unixes or ".dll" (dynamic link library) in Windows. When your programme is linked against a shared library, only a small table is created in the executable. Earlier the executable starts running, the operating system loads the motorcar code needed for the external functions - a process known as dynamic linking. Dynamic linking makes executable files smaller and saves disk space, because one re-create of a library can be shared between multiple programs. Furthermore, most operating systems allows one re-create of a shared library in memory to be used past all running programs, thus, saving memory. The shared library codes tin exist upgraded without the need to recompile your programme.

Because of the advantage of dynamic linking, GCC, by default, links to the shared library if it is available.

You tin list the contents of a library via "nm filename ".

Searching for Header Files and Libraries (-I, -L and -50)

When compiling the program, the compiler needs the header files to compile the source codes; the linker needs the libraries to resolve external references from other object files or libraries. The compiler and linker will not find the headers/libraries unless you set the appropriate options, which is non obvious for showtime-time user.

For each of the headers used in your source (via #include directives), the compiler searches the so-called include-paths for these headers. The include-paths are specified via -Idir option (or environs variable CPATH). Since the header's filename is known (east.m., iostream.h, stdio.h), the compiler only needs the directories.

The linker searches the then-chosen library-paths for libraries needed to link the programme into an executable. The library-path is specified via -Ldir option (uppercase 'L' followed past the directory path) (or environs variable LIBRARY_PATH). In improver, you also take to specify the library proper noun. In Unixes, the library libxxx.a is specified via -50xxx option (lowercase letter 'l', without the prefix "lib" and ".a" extension). In Windows, provide the total name such as -lxxx.lib. The linker needs to know both the directories every bit well every bit the library names. Hence, 2 options need to be specified.

Default Include-paths, Library-paths and Libraries

Try listing the default include-paths in your system used by the "GNU C Preprocessor" via "cpp -v":

>          cpp -v          ...... #include "..." search starts hither: #include <...> search starts here:  /usr/lib/gcc/x86_64-pc-cygwin/6.4.0/include
          /usr/include
          /usr/lib/gcc/x86_64-pc-cygwin/half dozen.4.0/../../../../lib/../include/w32api

Try running the compilation in verbose way (-5) to written report the library-paths (-Fifty) and libraries (-50) used in your system:

>          gcc -v -o hello.exe hello.c          ...... -L/usr/lib/gcc/x86_64-pc-cygwin/6.4.0 -Fifty/usr/x86_64-pc-cygwin/lib -L/usr/lib -L/lib -lgcc_s      -lgcc        -lcygwin     -ladvapi32   -lshell32    -luser32     -lkernel32


Eclipse CDT: In Eclipse CDT, yous can gear up the include paths, library paths and libraries past right-click on the projection ⇒ Properties ⇒ C/C++ General ⇒ Paths and Symbols ⇒ Under tabs "Includes", "Library Paths" and "Libraries". The settings are applicative to the selected project merely.

GCC Surroundings Variables

GCC uses the following environment variables:

  • PATH: For searching the executables and run-time shared libraries (.dll, .so).
  • CPATH: For searching the include-paths for headers. It is searched afterward paths specified in -I<dir> options. C_INCLUDE_PATH and CPLUS_INCLUDE_PATH can exist used to specify C and C++ headers if the particular language was indicated in pre-processing.
  • LIBRARY_PATH: For searching library-paths for link libraries. It is searched subsequently paths specified in -L<dir> options.

Utilities for Examining the Compiled Files

For all the GNU utilities, y'all can use " control --help" to list the help menu; or "human being command " to brandish the man pages.

"file" Utility - Determine File Type

The utility "file" tin exist used to display the type of object files and executable files. For example,

$          gcc -c hello.c          $          gcc -o how-do-you-do.exe hello.o          $          file hello.c          
howdy.c: C source, ASCII text, with CRLF line terminators  $          file hello.o          howdy.o: data   >          file hello.exe          hi.exe: PE32 executable (panel) x86-64, for MS Windows
"nm" Utility - Listing Symbol Table of Object Files

The utility "nm" lists symbol tabular array of object files. For example,

$          nm how-do-you-do.o          0000000000000000 b .bss
0000000000000000 d .information
0000000000000000 p .pdata
0000000000000000 r .rdata
0000000000000000 r .rdata$zzz
0000000000000000 t .text
0000000000000000 r .xdata
          U __main
0000000000000000 T main
          U puts  $          nm hi.exe | grep principal          
00000001004080cc I __imp___main
0000000100401120 T __main
00000001004010e0 T main
......

"nm" is commonly-used to check if a detail part is divers in an object file. A 'T' in the 2d column indicates a function that is defined, while a 'U' indicates a role which is undefined and should be resolved by the linker.

"ldd" Utility - List Dynamic-Link Libraries

The utility "ldd" examines an executable and displays a list of the shared libraries that it needs. For example,

>          ldd hullo.exe          ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ff9ba3c0000)
KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ff9b9880000)
KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ff9b6a60000)
SYSFER.DLL => /cygdrive/c/WINDOWS/System32/SYSFER.DLL (0x6ec90000)
ADVAPI32.dll => /cygdrive/c/WINDOWS/System32/ADVAPI32.dll (0x7ff9b79a0000)
msvcrt.dll => /cygdrive/c/WINDOWS/System32/msvcrt.dll (0x7ff9b9100000)
sechost.dll => /cygdrive/c/WINDOWS/System32/sechost.dll (0x7ff9b9000000)
RPCRT4.dll => /cygdrive/c/WINDOWS/System32/RPCRT4.dll (0x7ff9b9700000)
cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000)

GNU Make

The "brand" utility automates the mundane aspects of building executable from source code. "make" uses a so-called makefile, which contains rules on how to build the executables.

You can issue "brand --assist" to list the control-line options; or "man make" to display the man pages.

Outset Makefile By Case

Permit'southward begin with a unproblematic case to build the Hello-globe program (hello.c) into executable (hello.exe) via brand utility.

1 2 3 4 5 6 7
 
                    #include <stdio.h>   int master() {     printf("Hullo, world!\north");     return 0; }

Create the post-obit file named "makefile" (without whatsoever file extension), which contains rules to build the executable, and salve in the same directory as the source file. Use "tab" to indent the command (NOT spaces).

all: hi.exe  hello.exe: howdy.o 	 gcc -o howdy.exe hullo.o  hello.o: hi.c 	 gcc -c hello.c       make clean: 	 rm hello.o hello.exe

Run the "make" utility as follows:

>          make          gcc -c hello.c gcc -o howdy.exe hullo.o

Running make without argument starts the target "all" in the makefile. A makefile consists of a set of rules. A rule consists of iii parts: a target, a listing of pre-requisites and a command, equally follows:

          target:          pre-req-ane          pre-req-2          ...          control

The target and pre-requisites are separated past a colon (:). The command must exist preceded by a tab (NOT spaces).

When make is asked to evaluate a rule, it begins by finding the files in the prerequisites. If any of the prerequisites has an associated rule, brand attempts to update those first.

In the in a higher place example, the rule "all" has a pre-requisite "hullo.exe". make cannot find the file "hello.exe", so it looks for a dominion to create it. The dominion "hullo.exe" has a pre-requisite "hi.o". Again, it does not exist, so make looks for a rule to create it. The dominion "how-do-you-do.o" has a pre-requisite "hi.c". make checks that "hullo.c" exists and it is newer than the target (which does not exist). Information technology runs the command "gcc -c how-do-you-do.c". The rule "hello.exe" then run its command "gcc -o hi.exe hi.o". Finally, the rule "all" does nothing.

More than importantly, if the pre-requisite is not newer than than target, the command volition not be run. In other words, the command will be run only if the target is out-dated compared with its pre-requisite. For example, if we re-run the brand command:

>          brand          make: Aught to be done for `all'.

You tin also specify the target to be made in the make command. For example, the target "clean" removes the "how-do-you-do.o" and "hullo.exe". You tin can and so run the make without target, which is the same as "make all".

>          brand clean          rm hello.o howdy.exe   >          make          gcc -c hello.c gcc -o hello.exe hello.o

Try modifying the "how-do-you-do.c" and run make.

NOTES:

  • If the command is not preceded by a tab, you get an error message "makefile:iv: *** missing separator. Stop."
  • If there is no makefile in the current directory, you get an error message "make: *** No targets specified and no makefile establish. Cease."
  • The makefile can exist named "makefile", "Makefile" or "GNUMakefile", without file extension.

More than on Makefile

Annotate & Continuation

A annotate begins with a # and lasts till the end of the line. Long line tin can be broken and continued in several lines via a dorsum-slash (\).

Syntax of Rules

A general syntax for the rules is:

          target1          [target2          ...]: [pre-req-1          pre-req-two          ...] 	[command1          command2          ......]

The rules are commonly organized in such equally manner the more general rules come first. The overall dominion is oft proper noun "all", which is the default target for make.

Phony Targets (or Bogus Targets)

A target that does not represent a file is called a phony target. For case, the "clean" in the to a higher place instance, which is just a label for a command. If the target is a file, it will exist checked confronting its pre-requisite for out-of-date-ness. Phony target is ever out-of-date and its command volition be run. The standard phony targets are: all, clean, install.

Variables

A variable begins with a $ and is enclosed within parentheses (...) or braces {...}. Unmarried character variables do not need the parentheses. For example, $(CC), $(CC_FLAGS), $@, $^.

Automatic Variables

Automatic variables are set by make later on a dominion is matched. There include:

  • $@: the target filename.
  • $*: the target filename without the file extension.
  • $<: the first prerequisite filename.
  • $^: the filenames of all the prerequisites, separated by spaces, discard duplicates.
  • $+: similar to $^, but includes duplicates.
  • $?: the names of all prerequisites that are newer than the target, separated past spaces.

For case, we can rewrite the earlier makefile every bit:

all: howdy.exe   # $@ matches the target; $< matches the first dependent hullo.exe: hello.o 	gcc -o $@ $<  hullo.o: hullo.c 	gcc -c $<       clean: 	rm hullo.o howdy.exe
Virtual Path - VPATH & vpath

You can use VPATH (capital) to specify the directory to search for dependencies and target files. For example,

            VPATH = src include

You tin can also use vpath (lowercase) to be more precise almost the file type and its search directory. For example,

            vpath %.c src vpath %.h include
Design Rules

A pattern rule, which uses pattern matching character '%' every bit the filename, can be applied to create a target, if at that place is no explicit rule. For example,

            %.o: %.c 	$(COMPILE.c) $(OUTPUT_OPTION) $<    %: %.o $(LINK.o) $^ $(LOADLIBES) $(LDLIBS) -o $@
Implicit Pattern Rules

Make comes with a huge set of implicit pattern rules. You can list all the dominion via --print-data-base of operations option.

A Sample Makefile

This sample makefile is extracted from Eclipse's "C/C++ Development Guide -Makefile".

               LINK_TARGET = test_me.exe  OBJS =  \  Test1.o \  Test2.o \  Main.o   REBUILDABLES = $(OBJS) $(LINK_TARGET)   make clean :    rm -f $(REBUILDABLES)   echo Clean washed       all : $(LINK_TARGET)   echo All washed     $(LINK_TARGET) : $(OBJS)   thou++ -g -o $@ $^   %.o : %.cpp   g++ -g -o $@ -c $<   Main.o : Primary.h Test1.h Test2.h Test1.o : Test1.h Test2.h Test2.o : Test2.h   # %.dep : %.cpp #   m++ -M $(FLAGS) $< > $@ # include $(OBJS:.o=.dep)

Brief Summary

I have presented the basic brand features here so that you tin read and sympathise simple makefiles for building C/C++ applications. Make is really quite complex, and can be considered as a programming language by itself!!

REFERENCES & RESOURCES

  1. GCC Manual "Using the GNU Compiler Drove (GCC)" @ http://gcc.gnu.org/onlinedocs.
  2. GNU 'make' manual @ http://www.gnu.org/software/make/manual/make.html.
  3. Robert Mecklenburg, "Managing Projects with GNU Brand", tertiary Edition, 2004.

Latest version tested: CygWin GCC half-dozen.iv.0, MinGW-W64 GCC half-dozen.4.0
Final modified: March, 2018

mcilwraiththrooked.blogspot.com

Source: https://www3.ntu.edu.sg/home/ehchua/programming/cpp/gcc_make.html