James Mansion wrote: > Would there be any interest in collaboration on fixing this mess > so it all builds natively with CMake?
What is CMake? Is it perhaps a successor to nmake, found in the new MSVC packages? I think we really don't want to have to maintain two separate makefile systems. NSS formerly had an nmake file (named makefile.win) in every directory. But it was too limiting, and WAY too much work to keep in sync with the other Makefiles. It was easier to get gmake on windows than to maintain two Makefile systems. So we did that and eliminated the old makefile.win files. Seems to me that the real issue isn't gmake vs CMake, but rather concerns all the unix-line command line tools used in our builds. That's why we require Cygwin or MKS (or Mingw, or similar) sets of command line tools to build NSS today. But that's just my opinion. Let's see what others say. > I'd want to fix the import/export stuff too. I think a contribution to fix that stuff would be most welcome! > Might be worth retiring Win16 and Win95 now, too. Win16 should go, yes. The "Win95" stuff is really "Win32". It's stuff that is common to Win95/98/ME and also to NT/2K/XP. The "WinNT" stuff includes stuff that is only in NT/2k/XP. The mozilla browser today uses the Win95 stuff, not the NT stuff. > Looks like I need to revisit the manifests: I started by adding > pretty much everything that wasn't clearly an app. If possible, you may want to compare your build logs with the NSS build logs like this one: http://tinderbox.mozilla.org/showlog.cgi?log=NSS/1153465705.15157.gz to see if they're building the same files and doing the same steps. -- Nelson B _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
