1
edit
Changes
→Blur a window on a mochitest
</pre>
'''Answer 3''': Before cloning the repository, set the core.autocrlf to false input (which always checks things out with LF line endings) by using the following line.
<pre>
git config --global core.autocrlf falseinput
</pre>
Afterwards, you can freely clone the repository and the build should now work.
==Discussion=How do I resolve the error where CL cannot be found?=== This is the error that comes up: '''NorthWind87checking whether the C compiler (cl ) works... noconfigure:error: installation or configuration problem: C compiler cannot create executables.Fix above errors and then restart with "make -f client.mk build"make[1]: *** [configure] Error 1make[1]: Leaving directory `/d/proj/mozilla'make: *** [/d/proj/mozilla/obj-i686-pc-mingw32/Makefile] Error 2'' With regard ' <u>'''Answer 1:'''</u> This error is due to the .bat file not being able to find the vcvars32 or 64 file. This is because when we run the wrong .bat file.When the file says -x64 after it, for example 'start-msvc9-x64' it is not necessarily saying this needs to be run in a 64 bit operatingsystem but instead if you look inside the bat file you will see that this pretty much just means that it will be looking for the vcvarsfile in %VC9EXPRESSDIR%\bin\'''amd64'''\vcvars64.bat instead of Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat so make sure you are runningthe correct batch file and if you get this error check the path in the file to make sure it goes to the right place. ===How do I resolve the atlbase.h being missing?=== While running the "windows line make command, you get an error" questionsaying that atlbase.h file is missing! '''Answer 1:''' Apparently this is a very much known issue because apparently VS 2008 express does not come with this file, while the Professional version does come with it. Mozilla givesthe workaround of downloading the last version of of microsoft SDK which came with this file which is 2003. https://developer.mozilla.org/en/atlbase.h.After you install it not enough close and open the bat file again and rerun the make file. ===After building a debug version of Firefox on Windows, should I be seeing a lot of WARNING messages?===After a successful build, I launched Firefox Nightly, I got a command prompt screen that started outputting messages. Many of them are warning messages, should I be worried? Also, certain warnings (assertions) causes pop ups that need to be dealt with, is there a way to get rid of that? '''Answer 1''': No, the warning messages are normal. If you're using command prompt to simply start firefox.exe, you can type:<pre>set coreXPCOM_DEBUG_BREAK=warn</pre>NOTE: in a BASH shell you usually have to do it this way:<pre>export XPCOM_DEBUG_BREAK=warn</pre>That should suppress all pop ups. This is only necessary for windows.autocrlf Mac and Linux machines should be set to false this by default. ===Can't find header GL/glx.h for WebGL=== While running make, the following error presents itself:<blockquote>configure: error: Can't find header GL/glx.h for WebGL (install mesa-common-dev (Ubuntu), mesa-libGL-devel (Fedora), or Mesa-devel (openSUSE))) </blockquote>'''Answer 1''': This error is most likely caused by an error in your .mozconfig file. Make sure that all commands are prefixed properly with their correct add command (mk_add... or ac_add...) ===LNK 1210 Error=== While running make, the following error presents itself:<blockquote>LINK : fatal error LNK1210: exceeded internal ILK size limit; link with /INCREMENTAL:NO</blockquote>'''Answer 1''': This error is most likely caused by VC's incremental linking reaching its hard coded limit. To fix the problem, edit your '''config.in''' and corelocate the line #2505 find the following section of code, and insert '''-INCREMENTAL:NO''' options into LDFLAGS flag.eol <pre>if test $_MSC_VER -ge 1400; then LDFLAGS=”$LDFLAGS -LARGEADDRESSAWARE -NXCOMPAT -INCREMENTAL:NO“ dnl For profile-guided optimization PROFILE_GEN_CFLAGS=”-GL” PROFILE_GEN_LDFLAGS=”-LTCG:PGINSTRUMENT”</pre> ===How to pull new changes for mouselock===1. Copy the repo URL in git hub <br />2. git remote add <repo name> git://<url> <br />3. git checkout master, pull to master first to avoid conflict <br />4. git pull <repo name>/master <br />5. git checkout mouselock, change to mouse lock to merge with our up to date master. <br />6. git merge master <br /><br />To fix a merge conflict <br />1. git status, to see what files have an issue <br />2. git add <file>, fix then add those files <br />3. git commit ===Fixing rename errors in github===One problem that users can run into when trying to merge large number of files in github is the inability of renaming those files. The merge command on github have a limit to how much files can be renamed (not sure the exact limit, but I believe it is O^n limit). To increase the limit for large merge, users can re-set the upper limit with the help of the following command:<blockquote><pre>git config merge.renameLimit 999999</pre></blockquote>If you wish to lfre-set to the default limit afterwards, then do this:<blockquote><pre>git config --unset merge.renameLimit</pre></blockquote> ===How do I get a Document (nsIDocument) from a Window (nsIDOMWindow)?=== Answer: Given aWindow, an nsIDOMWindow*
<pre>
</pre>