C M S C 2 1 4
C o m p u t e r S c i e n c e I I
S p r i n g 2 0 0 4
|
Project #5 Checklist
Posted: April 15, 2004
There may be updates (including makefile, and a few reminders
before submitting).
You must submit the following files:
Do not put any of your files in a subdirectory before
tarring them
- .h files
- Vertex.h
- EndPoint.h
- Edge.h
- Graph.h
- .cpp files
- Vertex.cpp
- EndPoint.cpp
- Edge.cpp
- Graph.cpp
- main.cpp
- testVertex.cpp
- testEndPoint.cpp
- testEdge.cpp
- testGraph.cpp
Makefile
- Use macros, please! We should see things like:
CC = cxx
CFLAGS = -w0 -std strict_ansi -c
at the top of your makefile. Read the tutorial (click on
Tutorial on main webpage) for an example.
- Your first target should be p5
- Add testVertex.o,
testEndPoint.o, testEdge.o, and testGraph.o
to your dependencies for p5,
but
DON'T LINK THEM TO YOUR EXECUTABLE. Only link the .o files
needed by p4.
- You need to have lines to compile each of these .o files
with the -c options.
- When make p5 is called it creates the executable as
well as testVertex.o,
testEndPoint.o, testEdge.o, and testGraph.o.
- If you haven't written these test classes, then don't
generate the .o files for them. Create only the ones that you
wrote (which compile).
Reminders
- Did you use the main.cpp provided?
- Did you get the newest copies of the .h files?
- Did you add your own exceptions (to the main provided) in catch
clauses?
- Check the FAQs to make certain you have no incorrect
assumptions?
- Did you test your files?
- Make a temporary directory
- copy your tar file
- untar it
- run make
- copy the primary input and output
- run your program with primary input
- save the output
- diff the results with our output
- check to see that only blank lines differ, before submitting it.
- Is your executable called p5?
- Does your Makefile create .o files and LINK .o files?
See the class syllabus for policies concerning email
Last Modified:
Wednesday, March 10, 2004
|
|
|
|
|
|
Web Accessibility