Make lab answer

#An answer for the Make lab
#This makefile creates a simple program, uses the SUFFIX rule
#sets the compiler, flags and has a clean

CC = cc
CFLAGS = -g -DVIEW -I./include


all: get_it

get_it: first.o get_input.o
	$(CC) $(CFLAGS) first.o get_input.o -o get_it 

#For a dependency check you could do
first.o: ./include/myhdr.h
.SUFFIXES: .c .o
.c.o:
	$(CC) $(CFLAGS) -c $*.c
clean:
	rm -f *.o a.out

# Note that I used ./include  This is for ease of writing and portability.
# If I were to send this makefile along with the code for this lab, 
# I know that the header file will ALWAYS be in ./include because that is
# where setup puts it.  Now I don't have to worry about the user of the
# makefile having to be able to access my directory or the file system
# changing me some other home area because it will maintain this 
# relationship.  Those of you used something like
# $(HOME)/path/path/path/include 
# are also safe from the file movement problem but the code still
# wouldn't be as portable.  Don't worry, most of the time it is not
# issue because the code you write is only for your use, but it is something
# you need to remember when writing makefiles for classes.  Just where are
# those directories you referenced.  Can the TA access them? And are they
# really accessable using the path you specified?