1
edit
Changes
→Observations
The next hurdle was determining how to proceed after checking out the source files using the following command<pre>make -f client.mk checkout</pre> 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: <pre>make -f client.mk build</pre> which would initiate the build. Many thanks to [[User:Elichak|Liz Chak]] for providing me with this information. However, in defense of the mozilla build documentation, I must say that it is clearly stated there (in the [http://developer.mozilla.org/en/docs/Build_and_Install#Building Building section]) and I would have seen it had I read the documentation more thoroughly and perceived that those two commands (though similar) are not one and the same.
After the build completed I tried to launch firefox.exe (located within the C:\proj\mozilla\firefox-objdir\dist\bin folder). This opened up a console window, which scrolled through various pages after page of info before an error messages similar to the following. After finding no results on a google search, I decided to just click ignore for this message (and the 2 that followed seconds later). The console kept scrolling and a few seconds later a GUI Firefox Brower Application Window entitle Minefield opened ! After taking the required screen shots of the Help->About page, I decided to see if I could actually browse the web. This worked with no problems. Upon closing the GUI Minefield Browser Window received a few more of the error messages mentioned above. However, after clicking ignore on all of them, the console window proceed to close. After discussing the matter with a few others, to my relief I realized that I was not the only one receiving the same error messages during startup and exit.
=Conclusion=