1Relation between nss, moz, moz_prebuilt
2---------------------------------------
| 1Relation between nss, moz, moz_prebuilt
2---------------------------------------
|
3nss containes the security libraries which are also part of moz. However nss is
4meant to be more current, that is it to be updated more often. This should be
5easier than doing this with moz.
| 3nss contains the security libraries which are also part of moz. However nss is
4meant to be more current, that is, it to be updated more often. This
5should be easier than updating moz.
|
6
| 6
|
7If nss is build depends on an environment variable (ENABLE_NSS_MODULE=YES) which
8is per default set to YES. In this case nss is build before moz. The nss
| 7When nss is build, it depends on an environment variable (ENABLE_NSS_MODULE)
8which is by default set to YES. In this case nss is build before moz. The nss
|
9libraries/lib files/headers built in moz are then not delivered. Otherwise they
| 9libraries/lib files/headers built in moz are then not delivered. Otherwise they
|
10would overwrite those from nss. That is, the nss libraries build in moz are
| 10would overwrite those from nss. The nss libraries build in moz are then
|
11removed from mozruntime.zip (build in moz/solver/bin), they are removed from the
12lib directory (for example moz/unxlngi6.pro/lib), and the nss and nspr headers
13are also removed (inc/nss and inc/nspr). The nss libraries from the nss module
14are then added to mozruntime.zip.
15
16This also applies for moz_prebuilt. Therefore moz and moz_prebuilt must be build
17again after changes have been made to the libraries in the nss module.
18
19Also when moz was updated to use a newer version of mozilla, then one must make
20sure that new files which also belong to nss are not delivered and are removed
21from mozruntime.zip.
22
23Fips 140 and signed libraries
24-------------------------------
25Fips 140 mode is not supported. That is, the *.chk files containing the
26checksums for the cryptographic module are not delivered into solver and will
27not be part of the OOo installation sets.
28
29Signing has been turned off because
| 11removed from mozruntime.zip (build in moz/solver/bin), they are removed from the
12lib directory (for example moz/unxlngi6.pro/lib), and the nss and nspr headers
13are also removed (inc/nss and inc/nspr). The nss libraries from the nss module
14are then added to mozruntime.zip.
15
16This also applies for moz_prebuilt. Therefore moz and moz_prebuilt must be build
17again after changes have been made to the libraries in the nss module.
18
19Also when moz was updated to use a newer version of mozilla, then one must make
20sure that new files which also belong to nss are not delivered and are removed
21from mozruntime.zip.
22
23Fips 140 and signed libraries
24-------------------------------
25Fips 140 mode is not supported. That is, the *.chk files containing the
26checksums for the cryptographic module are not delivered into solver and will
27not be part of the OOo installation sets.
28
29Signing has been turned off because
|
30- we change the rpath (install names) after signing which breaks the signatures
| 30- we change the rpath (install names) after signing which breaks the signatures
|
31(Mac)
32- sqlite conflicts with the system sqlite when signing which breaks the build
33
34
35libfreebl3
36----------
37Porting to other platforms may require to deliver other variants of
38libfreebl*. The library name varies according to the platform. Changes need to
--- 37 unchanged lines hidden --- | 31(Mac)
32- sqlite conflicts with the system sqlite when signing which breaks the build
33
34
35libfreebl3
36----------
37Porting to other platforms may require to deliver other variants of
38libfreebl*. The library name varies according to the platform. Changes need to
--- 37 unchanged lines hidden --- |