The first problem I encountered related to downloading the source files. I was trying to figure out how this could be done i.e. via HTTP or FTP download or CVS. I was also trying to figure out if I would need the entire Mozilla source or simply that relating to firefox for the build. The answer to this problem was quite simple and common mistake. I realized that in my haste I failed to read the entire source download documentation before starting my attack. Upon reading the notes more carefully, I quicly learnt that CVS was the method of choice. To proceed with CVS I know had to re-run the Cygwin setup to install the CVS package that I had skipped initially (since I thought I would download the source via FTP/HTTP).
This brought I was still unable to logon to CVS. I was getting error messages saying that the CVS root was not specified even though I was issuing the commands specified in the Mozilla build documentation: cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/browser/config/mozconfig I found the answer to this problem in [Professor Humphreys][http://cs.senecac.on.ca/~david.humphrey/writing/firefox-win32-build.html Guide to building Firefox on Win32] The next hurdle was determining do after downloading the source. I spent a great deal of time at this juncture trying to extract various archives of the newly downloaded source via the Cygwin command prompt in a effort to start the build. I scoured through all the folders looking for an installer or build file. The most worrying part of this excercise was that I could not find my objdir even though I explicitly specified one in my .mozconfig file (i.e. firefox-objdir). Little did I know that I needed to issue a single command to proceed to the next step: make -f client.mk build which would initiate the build. Many thanks to Liz Chak for providing me to with the seinformation required.
=Conclusion=