Windows Prerequisites

  • Revision slug: Talk:Developer_Guide/Build_Instructions/Windows_Prerequisites
  • Revision title: Windows Prerequisites
  • Revision id: 2390
  • Created:
  • Creator: sdwilsh
  • Is current revision? No
  • Comment

Revision Content

Should the packages list also mention the "patch" and "cvs" packages? I remember being annoyed that it wasn't installed, but I'm not 100% sure that it was required to get patch. - DBaron 19:34:14, 2005-10-05 (PDT)

There is an older version of the MS PSDK from 2003 here. One user in the Mozillazine forums said he had better luck building with this than the newer one, which was released in 2005. - Napolj2 09:08:48, 2005-11-11 (PST)

I wanted to mention that I was compiling xulrunner on win2k with no OS service pack, and the compile was dying during the final link of the toolkit. I tried numerous things to get the compile to work, but they all failed. I then installed the win2k SP4, and after this the build worked. This led me to wonder if the Hardware Requirements section was incomplete. Perhaps a service pack is needed? - Briprowe 15:43, 12 December 2005 (PST)

Can somebody explain why choosing DOS line endings is recommended? The cygwin manual strongly recommends against them "unless you have a very good reason to switch". Momoko 07:16, 19 December 2005 (PST)

As for the MS PSDK, Microsoft explicitly warns that the one linked to in the main page (Windows 2003 Server SP1 PSDK) does {{mediawiki.external('b')}}not{{mediawiki.external('/b')}} work with Visual C++ 6.0. I made a mistake of not reading the 'not-so-fine' print in the page and installing it only to get a link error while compiling xpcom. Fortunately, I installed it in a different directory from the directory where Feb. 2003 edition of SDK was installed so that I could just revert to the old PSDK changing environment variables, PATH, LIB and INCLUDE without doing the chore of reinstalling it. Jshin 2006-02-03 10:42 (UTC)

Shouldn't binutils be listed under necessary cygwin patches or at least recommended for non-debug builds? Autoconfig will detect that strip isn't available and happily continue but installing binutils and making strip.exe available greatly reduces the resultant binaries... -Jay Lee


I think you need to add the Make package to the list of things needed after default. Doing the default didn't have Make for me at least. comrade693

Revision Source

<p>Should the packages list also mention the "patch" and "cvs" packages?  I remember being annoyed that it wasn't installed, but I'm not 100% sure that it was required to get patch. - <a href="User:DBaron">DBaron</a> 19:34:14, 2005-10-05 (PDT)
</p><p>There is an older version of the MS PSDK from 2003 <a class="external" href="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm">here</a>.  One user in the Mozillazine forums said he had better luck building with this than the newer one, which was released in 2005. - <a href="User:Napolj2">Napolj2</a> 09:08:48, 2005-11-11 (PST)
</p><p>I wanted to mention that I was compiling xulrunner on win2k with no OS service pack, and the compile was dying during the final link of the toolkit.  I tried numerous things to get the compile to work, but they all failed.  I then installed the win2k SP4, and after this the build worked.  This led me to wonder if the Hardware Requirements section was incomplete.  Perhaps a service pack is needed? - <a href="User:Briprowe">Briprowe</a> 15:43, 12 December 2005 (PST)
</p><p>Can somebody explain why choosing DOS line endings is recommended? The cygwin manual strongly recommends against them "unless you have a very good reason to switch". <a href="User:Momoko">Momoko</a> 07:16, 19 December 2005 (PST)
</p><p>As for the MS PSDK, Microsoft explicitly warns that <a class="external" href="http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&amp;displaylang=en">the one linked to in the main page (Windows 2003 Server SP1 PSDK)</a> does {{mediawiki.external('b')}}not{{mediawiki.external('/b')}} work with Visual C++ 6.0. I made a mistake of not reading the 'not-so-fine' print in the page and installing it only to get a link error while compiling xpcom. Fortunately, I installed it in a different directory from the directory where <a class="external" href="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm">Feb. 2003 edition of SDK</a> was installed so that I could just revert to the old PSDK changing environment variables, PATH, LIB and INCLUDE without doing the chore of reinstalling it. <a href="User:Jshin">Jshin</a> 2006-02-03 10:42 (UTC)
</p><p>Shouldn't binutils be listed under necessary cygwin patches or at least recommended for non-debug builds?  Autoconfig will detect that strip isn't available and happily continue but installing binutils and making strip.exe available greatly reduces the resultant binaries... -Jay Lee
</p><p><br>
I think you need to add the Make package to the list of things needed after default.  Doing the default didn't have Make for me at least. <a href="User:Comrade693">comrade693</a>
</p>
Revert to this revision