#### # # This is a sample Makefile template for building projects in a Fisher project # directory structure using the InterViews GUI toolkit. Search for "CHANGE # HERE" to see the places to make changes for a particular project. When # you've made the changes, remove the "CHANGE HERE" comments. Also when you've # made all changes, remove the header comment and replace with an appropriate # comment of your own, describing what the Makefile does. "E.g., "Makefile for # building the XXX tool". # # For a concrete example of this Makefile, see the rololdex project Makefile in # # ../../rolodex/implementation/$(PLATFORM)/Makefile # # where PLATFORM is defined below. # # # Model object files. # # CHANGE HERE by putting the names of your model object files in place of # model-file1.o, model-file2.o, etc. List the files in alphabetic order. Make # sure that each line except the last ends with a backslash character. # MODEL_OBJS = \ model-file1.o \ model-file2.o # etc. # # View object files. # # CHANGE HERE by putting the names of your view object files in place of # view-file1.o, view-file2.o, etc. List the files in # alphabetic order. Make sure that each line except the last ends with a # backslash character. # VIEW_OBJS = \ view-file1.o \ view-file2.o # etc. # # Process object files. # # CHANGE HERE by putting the names of your process object files in place of # process-file1.o, process-file2.o, etc. Leave the main.o file; this is where # function main for the full system is declared. List the files in alphabetic # order. Make sure that each line except the last ends with a backslash # character. Note that # PROCESS_OBJS = \ main.o \ process-file1.o \ process-file2.o # etc. # # All of the object files. # ALL_OBJS = $(MODEL_OBJS) $(VIEW_OBJS) $(PROCESS_OBJS) # # Relative paths to design and implementation directories. # DESIGN_DIR = ../../design IMPLE_DIR = .. # # Platform type. Use to specify what platform the make is on. At Cal Poly, # the following platform names are used: # # SUN4G: SUN4s galaxy and phoenix # SUN4K: SUN4 kdat # HP700: HP 700 cobra cluster # HP400: HP 400 garden cluster # # Note that on kdat, the SUN4K directory may not always exists. If it does # not, the SUN4G directory holds the executables. This is because # galaxy/phoenix executables will run on kdat, but in order to make native on # kdat, a different makefile is need to accomodate differences between kdat # and galaxy, such as absolute file paths. # PLATFORM = SUN4G # # Paths to relevant root project directories # LEVEL = alpha PROJECTS_DIR = /home/phoenix/faculty1/gfisher/projects/$(LEVEL) PROJECTS_INCLUDE_DIR = $(PROJECTS_DIR)/include PROJECTS_LIB_DIR = $(PROJECTS_DIR)/lib/$(PLATFORM) SUPPORT_DOC_DIR = $(PROJECTS_DIR)/support/documentation # # Paths to the relevant directories of the InterViews GUI toolkit # IV_DIR = $(PROJECTS_DIR)/interviews IV_INCLUDE_DIR = $(IV_DIR)/design IV_LIB_DIR = $(IV_DIR)/implementation/libInterViews/$(PLATFORM) IV_LIB_GRAPHICS_DIR = $(IV_DIR)/implementation/libgraphic/$(PLATFORM) # # InterViews libraries; the _g version is compiled with debugging on, so that # GUI library functions can be traced if necessary. # IV_LIBS = $(IV_LIB_DIR)/libInterViewsX11.a $(IV_LIB_DIR)/libgraphic.a IV_LIBS_g = $(IV_LIB_DIR)/libInterViewsX11-g.a \ $(IV_LIB_GRAPHICS_DIR)/libgraphic-g.a # # X Windows and other system libraries. # X_LIB = -lX11 # X Windows lib OTHER_LIBS = -lsupport \ -liv-local \ -lm -lg++ -lgen # # Compilation flags and related definitions # CFLAGS = -c -g \ -I$(DESIGN_DIR) -I$(PROJECTS_INCLUDE_DIR) -I$(IV_INCLUDE_DIR) \ -Dgcc_2_6_3 -fhandle-exceptions LDFLAGS = -g -L/usr/openwin/lib -L$(PROJECTS_LIB_DIR) CC = g++ GCC = gcc LIBS = $(IV_LIBS) $(X_LIB) $(OTHER_LIBS) LIBS_g = $(IV_LIBS_g) $(X_LIB) $(OTHER_LIBS) DEPEND_SRCS = $(IMPLE_DIR)/*.C DEPEND_FLAGS = -I$(DESIGN_DIR) -I$(PROJECTS_INCLUDE_DIR) -I$(IV_INCLUDE_DIR) \ -Dgcc_2_6_3 # # Default definition to make. # # CHANGE HERE by changing "your-tool" to the name of the executable # file for your tool # default: your-tool # # Build a complete tool. # # CHANGE HERE by changing "your-tool" to the name of the executable # file for your tool # your-tool: $(ALL_OBJS) $(CC) $(LDFLAGS) $(ALL_OBJS) $(LIBS_g) -o your-tool # # Build the design only, which means just compile the .h files, all of which # are included in compile-stub.C. # design: $(CC) $(CFLAGS) $(DESIGN_DIR)/compile-stub.C # # CHANGE HERE by adding additional make rules, e.g., for building stubbed-out # testing versions of the tool. See the rolodex project Makefile for an # example. # # # Generic pattern rules to make all of the implemenation files. # %.o: $(IMPLE_DIR)/%.C $(CC) $(CFLAGS) $< %.E: $(IMPLE_DIR)/%.C $(CC) -E $(CFLAGS) $< > $*.E # # Delete all object files. # # CHANGE HERE by changing "your-tool" to the name of the executable # file for your tool # clean: rm -f *.o your-tool # # Generate dependencies using makedepend. # depend: $(DEPEND_SRCS) makedepend $(DEPEND_FLAGS) $? # # Generate printable PostScript output for source files. Format is two-column # 7 point courier font in landscape page layout. # print: print_design print_implementation print_support # # CHANGE HERE by changing "your-tool" to the name of the executable # file for your tool # print_design: csh -f -c "cd $(DESIGN_DIR); \ $(SUPPORT_DOC_DIR)/codeprint2.csh \ ../documentation/formatted-code \ your-tool/design \ *.h" # # CHANGE HERE by changing "your-tool" to the name of the executable # file for your tool # print_implementation: csh -f -c "cd $(IMPLE_DIR); \ $(SUPPORT_DOC_DIR)/codeprint2.csh \ ../documentation/formatted-code \ your-tool/implementation \ *.C" print_support: csh -f -c "cd $(PROJECTS_INCLUDE_DIR) ; \ ../support/documentation/codeprint2.csh \ ../rolodex/documentation/formatted-code \ support/design \ view.h model.h" # DO NOT DELETE THIS LINE -- make depend depends on it.