1
edit
Changes
→Lets go through the steps
==Lets go through the steps==
'''1st ''' - checkout the code from the repository...
'''2nd ''' - the The organizer must add the following files to the repository.the The io_def.h with ciol.h included for cpp in there (with extern and everything) and a prjmain.cpp file with a main and 8 "sub-main" functions for each developer. You can call those functions like: int neda_main() or canton_main() and so on. The real main function (main) should use have only one function call in it to one of those sub-main functions.
Each of you can have his/her own main to test what they are developing and update and commit will not ruin other developer's main. The only thing you need to do after an update, is to change on function call in main.
'''3rd ''' - choose the best ciol written and add it to the repository or m (all these are being added to the PRJ directory)
When I say add the file to repository, all you do is to add the file to your working copy and then issue svn add filename (or right-click on it and then svn add) and the svn commit. Remember when you add a file, it will be marked to be added on next commit.
'''4th ''' - each Each developer checks out the code and then adds a "your_name".txt to the Docs dir in PRJ. This file is used as a log to register all you do currently, most recent task is on topthen the organizer will assign classes to each developer from thedefinition of assign 2.
All you do first is to create a header file and cpp file with the same name as the class name, and then build the working copy and make sure it compiles. When you reached to a build-able stage, you commit the code so other developers can get the class in next update.
'''NEVER COMMIT A CODE THAT DOES NOT COMPILE. ''' Your PRJ must always be build-able.
You have your own main testing your own class, it is at the finalstages of the project where you work on the same main
So what I want to see by next meeting:
The full repository created made build-able with all the classesmentioned in as2 desc. Just create the header-file and cpp file. Ineed to know who created which class by looking at the docs directory and your logs.
I expect you all to blog about this meeting.
You can look at other teams wikis for ideas and you should give ideas and suggestions to others...
=To Do=
