James Mansion wrote: > I downloaded this source package with a view to building it on XP. > > I can't see any native XP build support for much of the system - is a VS2003 > build supported at all? There's a README in the coreconf directory, but its > not clear entirely clear what's necessary to bootstrap.
Building NSS and/or NSPR requires the use of a package of unix-like tools for windows, such as MKS toolkit or Cygwin. It uses gmake 2.79.1 or 2.80 to do the makes. Can use MSVC or gcc compilers. Known to build with VC5, VC6 or VC8 (that is "express") IINM. > Is theer an idiot's guide anywhere? There should be a page on www.mozilla.org that explains all this. In fact, there are probably a lot of them, and the trick is finding the current one. Maybe this page will help: http://www.mozilla.org/projects/security/pki/nss/nss-3.7.7/nss-3.7.7-build.html [snip] > And, at line 1079 of p12exp.c, the call to SEC_PKCS7CreateEncryptedData has > only 3 arguments, while its defined at line 304 of secpkcs7.h with 4 > arguments. p12exp.c is dead. It is not built. Should be removed. See the directory's manifest.mn file for a list of files being actively built. Every directory (with very few exceptions) has its own makefile and its own manifest. The latter defines the sources that are built, the public header files that are "exported", etc. NSS controls which symbols are exported from shared libs using a "def" file. That is, the "link" command line that builds the DLLs takes a symbol definitions file (specified as -DEF:<directory>:<libname>.def I think you'll find that the symbol whose name you mentioned (nssCKFWHash_Add) isn't listed in any .def file, and therefore is not actually exported despite the dllexport designation. > So - there's been a bit of head scratching here. Hope this helps you get started. -- Nelson B _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
