Changes between Version 24 and Version 25 of BuildingWinNSS

Timestamp:

Mar 5, 2010, 1:16:45 AM (14 years ago)

Author:

John Bailey

Comment:

Some tweaks to the wiki formatting, and note incompatibilities with 64-bit NSS or Visual C++ compiled NSS and Pidgin

BuildingWinNSS

@@ -5 +5 @@
 NSS stands for [http://www.mozilla.org/projects/security/pki/nss/ Network Security Services]. NSS is required to use SSL in Pidgin. NSS depends on NSPR and a [https://wiki.mozilla.org/NSS_Shared_DB shared database] (SQLite since [http://www.mozilla.org/projects/security/pki/nss/nss-3.12/nss-3.12-release-notes.html NSS 3.12]), but you don't have to worry about these, there's and NSS with NSPR package which is compact thus it contains all sources required to build NSS.
 
-'''Note''': at the moment you can't build NSS completely using GCC. It fails at the final stage when linking additional tools. However, you can build all the important libraries successfully. It will hopefully be improved in the future. You can build NSS completely with [http://www.microsoft.com/downloads/details.aspx?FamilyId=F3FBB04E-92C2-4701-B4BA-92E26E408569&displaylang=en#filelist Microsoft Visual C++ 2008 Express Edition SP1]. This isn't covered in this tutorial but it's basically the same. However, if you build NSS with Visual C++, you must instruct your users to install the [http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Microsoft Visual C++ 2008 SP1 Redistributable Package] or include it in the installer of your application (if permitted).
+'''Note''': at the moment you can't build NSS completely using GCC. It fails at the final stage when linking additional tools. However, you can build all the important libraries successfully. It will hopefully be improved in the future. You can build NSS completely with [http://www.microsoft.com/downloads/details.aspx?FamilyId=F3FBB04E-92C2-4701-B4BA-92E26E408569&displaylang=en#filelist Microsoft Visual C++ 2008 Express Edition SP1]. This isn't covered in this tutorial but it's basically the same. However, if you build NSS with Visual C++, you must instruct your users to install the [http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Microsoft Visual C++ 2008 SP1 Redistributable Package] or include it in the installer of your application (if permitted).  Note that you cannot use NSS with Pidgin if it is built with Visual C++, as the mingw GCC and Visual C++'s compiler link against different, incompatible C libraries.
 
 == Prerequisites ==
 
- 1. Get NSS
-
-  Download [ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_5_RTM/src/nss-3.12.5-with-nspr-4.8.2.tar.gz NSS with NSPR 3.12.5]. Extract it to `c:\devel\pidgin-devel\win32-dev`.
-
- 2. Get !MozillaBuild
-
-  Download [http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.4.exe MozillaBuild 1.4] and install it to `c:\devel\mozilla-build`.
-
- 3. Get MinGW
-
-  This assumes that you have MinGW working as described in the [wiki:BuildingWinPidgin#Themanualway Pidgin Building Instructions] (in short, you need [https://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/ MinGW] installed with at least gcc).
+ 1. '''Get NSS:'''  Download [ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_5_RTM/src/nss-3.12.5-with-nspr-4.8.2.tar.gz NSS with NSPR 3.12.5]. Extract it to `c:\devel\pidgin-devel\win32-dev`.
+ 1. '''Get MozillaBuild:'''  Download [http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.4.exe MozillaBuild 1.4] and install it to `c:\devel\mozilla-build`.
+ 1. '''Get MinGW''':  This assumes that you have MinGW working as described in the [wiki:BuildingWinPidgin#Themanualway Pidgin Building Instructions] (in short, you need [https://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/ MinGW] installed with at least gcc).
 
 == Choose build flavour ==
 
 The 3 most important options are:
-
  * target OS
  * optimization
@@ -30 +21 @@
 
 You can toggle them with environmental variables. Here's the matrix:
-
-{{{
+   {{{
 #!comment
-||||BUILD_OPT=0||BUILD_OPT=0||BUILD_OPT=1||BUILD_OPT=1||
-||||USE_DEBUG_RTL=0||USE_DEBUG_RTL=1||USE_DEBUG_RTL=0||USE_DEBUG_RTL=1||
+|| ||BUILD_OPT=0||BUILD_OPT=0||BUILD_OPT=1||BUILD_OPT=1||
+|| ||USE_DEBUG_RTL=0||USE_DEBUG_RTL=1||USE_DEBUG_RTL=0||USE_DEBUG_RTL=1||
 ||OS_TARGET=WIN95||WIN954.0_DBG.OBJ||WIN954.0_DBG.OBJD||WIN954.0_OPT.OBJ||N/A||
 ||OS_TARGET=WINNT||WINNT6.1_DBG.OBJ||WINNT6.1_DBG.OBJD||WINNT6.1_OPT.OBJ||N/A||
-}}}
-
-{{{
+   }}}
+   {{{
 #!rst
 
@@ -51 +40 @@
 =================  =================  =================  =================  =================
 
-}}}
+   }}}
 
 The version after WINNT is the version of your current OS (you can check it with the `winver` command). WINNT6.1 assumes you're building on Windows 7.
@@ -58 +47 @@
 
 Pick the desired configuration (in other words, cell), and set the environmental variables with `set`. Example:
-
-{{{
+   {{{
 set BUILD_OPT=1
 set OS_TARGET=WIN95
-}}}
+   }}}
 
 '''WARNING''': it seems the builder considers any variable as 1 if it's set. So if you enter
-
-{{{
+   {{{
 set BUILD_OPT=0
-}}}
-
+   }}}
 you'll get an optimized build although you wanted a debug one. The answer lies in `mozilla\security\coreconf\WIN32.mk`. They check variables with ifdefs, which is just plain wrong (or they should mention it this way in the documentation).
 
 '''Solution''': set a variable only if you want the related build. Here's the table for seeing what you actually have to enter and what you'll get:
-
-||||||USE_DEBUG_RTL=1||BUILD_OPT=1||
-||OS_TARGET=WIN95||WIN954.0_DBG.OBJ||WIN954.0_DBG.OBJD||WIN954.0_OPT.OBJ||
-||OS_TARGET=WINNT||WINNT6.1_DBG.OBJ||WINNT6.1_DBG.OBJD||WINNT6.1_OPT.OBJ||
-
+   || || ||USE_DEBUG_RTL=1||BUILD_OPT=1||
+   ||OS_TARGET=WIN95||WIN954.0_DBG.OBJ||WIN954.0_DBG.OBJD||WIN954.0_OPT.OBJ||
+   ||OS_TARGET=WINNT||WINNT6.1_DBG.OBJ||WINNT6.1_DBG.OBJD||WINNT6.1_OPT.OBJ||
 OS_TARGET is an exception and isn't affected by this error because it's not numerical, so the script checks for its value instead of its existence. As a sidenote, BUILD_OPT seems to have a higher priority than USE_DEBUG_RTL, so if you enter
-
-{{{
+   {{{
 set BUILD_OPT=1
 set USE_DEBUG_RTL=1
-}}}
-
+   }}}
 you'll get an optimized build without linking with the debug RTL. In case you want, for example, a debug build after an optimized, you can unset the variable by setting it without a value, such as:
 
-{{{
+   {{{
 set BUILD_OPT=
-}}}
+   }}}
 
 More info about the build variables can be found on the [https://developer.mozilla.org/en/NSS_reference/Building_and_installing_NSS/Build_instructions Build instructions] page of the Mozilla Developer Central.
@@ -168 +150 @@
   * Visual C++ Compilers
   * Win32 Development Tools
+ 1. Start `Microsoft Windows SDK v7.0/CMD Shell` from the Start Menu. Don't be bothered by the message about target, it won't affect this build. If it really annoys you, you can tweak it with `setenv` (query flags with `setenv /?`).
+ 1. Find a way to include `moztools\bin` and `msys\bin` in PATH.
+ 1. Set build flavour as before, and additionally add the following:
+   {{{
+set USE_64=1
+   }}}
+ 1. Start compiling:
+   {{{
+make nss_build_all
+   }}}
+ 1. Instruct your users to download and install the [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ba9257ca-337f-4b40-8c14-157cfdffee4e Microsoft Visual C++ 2008 SP1 x64 Redistributable Package] or include it in the installer of your application (if permitted).
 
- 2. Start `Microsoft Windows SDK v7.0/CMD Shell` from the Start Menu. Don't be bothered by the message about target, it won't affect this build. If it really annoys you, you can tweak it with `setenv` (query flags with `setenv /?`).
-
- 3. Find a way to include `moztools\bin` and `msys\bin` in PATH.
-
- 4. Set build flavour as before, and additionally add the following:
-
-{{{
-set USE_64=1
-}}}
-
- 5. Start compiling:
-
-{{{
-make nss_build_all
-}}}
-
- 6. Instruct your users to download and install the [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ba9257ca-337f-4b40-8c14-157cfdffee4e Microsoft Visual C++ 2008 SP1 x64 Redistributable Package] or include it in the installer of your application (if permitted).
+Note that it's not possible to use a 64-bit version of NSS with Pidgin on Windows.  Pidgin is a 32-bit application, thus cannot interact with 64-bit libraries.