15-410 Project 1 Hand-in

1. Your files should be placed in your p1 directory, not somewhere else, such as hw1. If you haven't stored files in your AFS volume yet, please refer to About your 15-410 AFS Space for help if you run into trouble. We are not responsible if you wait until 23:50 to try out your AFS volume and run into trouble.

2. Please do not add levels of indirection when turning in your files. For example, do not place your game_kern_main.c in p1/proj1/kern/game_kern_main.c or turn in p1/my_project_one.tar. Please use the most straightforward arrangement, i.e., p1/kern/game_kern_main.c.

3. When the deadline arrives, we will write-lock your hand-in directory. You will continue to be able to view the contents.

4. When we grade your work, we will overwrite files which are not in kern/ with a mixture of the files which update.sh installed for you. We will then add and modify some files. This means that you must confine your modifications to files located in kern/, with the exception of config.mk. You should make sure you have followed all the directions in config.mk carefully, and that make clean followed by make will build both the game and the tester properly (we may deduct points if your assignment doesn't build "out of the box"). Please make veryclean in your handin directory after turning in your files--the AFS space you save will be your own! See Grading Makefile and Dual Images for more information. Recall that, no matter what flavor of machine you used to prepare your assignment, it must build and run on Andrew cluster Linux machines.

5. You must also make sure that make html_doc and make print do the right thing.

6. Your deliverables are:

   • Various .c and .S files (located in kern/).
   • .h files (located in kern/inc/).
   • README.dox
   • Any *.mk files -- since you needed to configure them for your project to build/print/etc., if you don't turn them in, your project won't build/print/etc....

   Please do not include:

   • .o files
   • executable files such as game, 410test
   • .img files
   • fake.c

   Things not mentioned on either list above (the 410kern/ directory, etc.) are at your discretion. You can assume that if we gave them to you once we won't mind giving them to you again.

   You can roughly simulate how we will build your code as follows:

   1. % cd /afs/cs.cmu.edu/academic/class/15410-f13/usr/$USER/p1
   2. % make clean
   3. % make update
   4. % make
   5. % make html_doc
   6. % make veryclean
   7. % du -sk .

   The "du" step reports the disk space usage of the directory you're in, in kilobytes. Anything over 2048 kilobytes for Project 1 probably means you're turning in something unnecessary. The final "make veryclean" should leave things in a nice hand-in state.

7. If you need to take a late day for Project 1 (you shouldn't!), use the Late Day Registration Page, by roughly 00:30. Assuming your message is received, the next morning somebody will unlock your hand-in directory so you can again save your work. Of course, your request must be in accordance with the policy published in the syllabus.

[Last modified Friday September 06, 2013]