CS11 – Introduction to C++.PDF

CS11 Intro C++ Spring 2018 – Lecture 4 Build Automation • When a program grows beyond a certain size, compiling gets annoying… g++ -std=c++14 -Wall units.cpp testbase.cpp \ hw3testunits.cpp -o hw3testunits g++ -std=c++14 -Wall units.cpp convert.cpp -o convert • Also, if only units.cpp changes, why recompile testbase.cpp/ hw3testunits.cpp / convert.cpp source files? • Typical development process: • Write or modify some code • Compile • Test • Repeat until done… • Automating this process saves lots of time and effort 2 make • make is a standard tool for automating builds • Command-line utility, very ubiquitous! • Takes input files and produces output files, based on a “makefile” • Several versions of make : GNU, BSD, … • make is often used for C and C++ projects • Sometimes other build tools are used for C/C++ • CMake is becoming increasingly popular • Visual C++ provides nmake command-line build program • Other languages typically have their own build tools 3 Makefiles • make requires a makefile that describes how to build your program • Typical filenames are Makefile (preferred) or makefile • Can specify a nonstandard makefile name with: make -f some-other-makefile • The makefile describes build targets • Files that need to be generated from other files • Each target specifies its dependencies – the files needed to build the target • Can also specify how to build the target from its dependencies 4 Example Makefile • Example Makefile: convert : units.o convert.o g++ -std=c++14 -Wall units.o convert.o \