Changes between Initial Version and Version 1 of BuildingWinNSS

Timestamp:

Feb 28, 2010, 5:10:45 PM (14 years ago)

Author:

bviktor

Comment:

--

BuildingWinNSS

@@ +1 @@
+= Building NSS on Windows =
+
+== Preamble ==
+
+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 shared database (SQLite since 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.
+
+== 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 so somewhere (you'll get an `nss-3.12.5-with-nspr-4.8.2` directory).
+
+ 2. Get MozillaBuild
+
+  Download [http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.4.exe MozillaBuild 1.4] and install it. By default it installs to `c:\mozilla-build`. Add `c:\mozilla-build\msys\bin` and `c:\mozilla-build\moztools\bin` to your PATH.
+
+ 3. Get MinGW
+
+  Download a recent build of the [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/sezero_20100223/mingw-w32-bin_i686-mingw_20100223_sezero.zip/download MinGW-w64 w32 toolchain]. Extract it to `c:\mozilla-build\msys` so that MSYS and MinGW have the same folder hiearchy (e.g. MinGW binaries go to `c:\mozilla-build\msys\bin` etc.).
+
+ 4. Get Visual C++ Express
+
+  Download [http://www.microsoft.com/downloads/details.aspx?FamilyId=F3FBB04E-92C2-4701-B4BA-92E26E408569&displaylang=en#filelist Visual C++ 2008 Express Edition SP1] (vcsetup.exe). Install without SQL Server (you can install it, but it's not required for building NSS).
+
+== Start build environment ==
+
+ 1. Run Visual Studio 2008 Command Prompt from Start Menu.
+
+ 2. Go to `nss-3.12.5-with-nspr-4.8.2\mozilla\security\nss`.
+
+== Choose build flavour ==
+
+The 3 most important options are:
+
+ * target OS
+ * optimization
+ * debug RTL
+
+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||
+||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
+
+=================  =================  =================  =================  =================
+        .                      BUILD_OPT=0                           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
+=================  =================  =================  =================  =================
+
+}}}
+
+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.
+
+The default values are 0 for numerical variables and current OS for OS_TARGET. So on Windows 7 with no values set you'll end up building WINNT6.1_DBG.OBJ.
+
+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||
+
+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, 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 in the [https://developer.mozilla.org/en/NSS_reference/Building_and_installing_NSS/Build_instructions Build instructions] page of the Mozilla Developer Central.
+
+== Build NSS ==
+
+Enter
+
+{{{
+make nss_build_all
+}}}
+
+The resulting binaries will be placed in `nss-3.12.5-with-nspr-4.8.2\mozilla\dist`.