Well here's the procedure I've been using.
The philosophy behind it is based on when I used to do formal releases of software. It can be summarized as "Clean get, clean build." It gives you a fresh start. The releases I used to do were the definitive, single source, final build for a given version.
I use Xcode version 3.1.2 to do the actual build. I'm not in a position to talk about other versions of Xcode.
1) Start with a clean development folder. My own development path is "/users/<user name>/development/warzone2100". Yours may be different. I shall reference this as <development path> below.
2) Run Terminal.
3) Enter the command "cd <development path>".
4) Enter the command "svn co
https://warzone2100.svn.sourceforge.net ... 100/trunk/".
The first time you do this, you will get a prompt on whether or not to accept the repository's SSL certificate.
Enter 'p' to accept the certificate permanently, 't' to accept the certificate temporarily, or 'd' to reject the certificate. In the case of the latter, the download will abort. I used the 'p' option that first time, and I haven't had this prompt since.
This takes a while, so now is a good time to make a cup of tea.
5) Change to the trunk directory. In my case this would be "cd <development path>/trunk".
6) Enter the command "svn co
https://quesoglc.svn.sourceforge.net/svnroot/quesoglc".
This too can take a while, but not as long as the previous get. In fact you can run this from a separate Terminal instance.
The downloads, incidentally, will finish by reporting the corresponding code revisions.
At this point, you can logout from and exit Terminal.
7) Now, I can't successfully build Warzone without replacing a couple of OpenGL files; GLee.h and GLee.c. The .zip file below contains these. These should be copied into the "<development path>/trunk/lib/ivis_opengl" directory. These originate from the GL Easy Extension library webpage.
Run Xcode.
9) From Project->Open find and open the file Warzone.xcodeproj. Using my development directory as an example, the path to this location is "<development path>/trunk/macosx".
You can, from Finder, just double-click on the file. That works too.
10) Select the type of build you want to perform. Your options are "Release" or "Debug." Look for the "Active Build Configuration" label.
At this point, from Xcode, I like to do Build->Clean all targets.
11) Then either click on the Build icon or, from the menu, do Build->Build. Time for another cup of tea.
If you get errors, along the lines of "error: 'GLee_FuncPtr_glBindBuffer' undeclared (first use in this function) then you didn't perform step 7. Go back and rectify the situation, then restart the build.
12) You should get the message "Build Succeeded."
In principle, that should be it. You will find your Warzone.app file either in "<development path>/macosx/build/release" or "<development path>/macosx/build/debug" depending upon the type of build you performed.
However, if you get other errors, that previously you hadn't been getting, going back to step one might be a good idea. Indeed, during the writing of this document, trunk release 7588 broke my compilation. The next release, version 7589, downloaded a few minutes later, put things right again. If this happens during what is supposed to be a release build, evisceration is a recommended course of action, or defenestration. Both have their appeal.
You do not have the required permissions to view the files attached to this post.
