Christopher Seawood wrote:
Ljósálfr wrote:
Is there a reason that nss is disabled at the end of the configure.in as shown here?
Because we don't need/use ldap's ssl-enhanced library when building ldap for mozilla. The --without-nss only applies to ldap. NSS is still built for Mozilla if you use the --enable-crypto flag.
- cls
That still doesn't build all of NSS does it?
No, we do not build all of NSS when building Mozilla. We just build the libraries and the one cmdline utitily that we need. If you want to build all of NSS, you should use the NSS standalone build instructions.
I built it the other day, and after figuring out how to pretend to be an install script I was able to put it in my $PATH and /etc/ld.so.conf. (Then I made the mistake of looking at Cert-O-Matic.... Oh my....) What I'd really like is to be able to tell the client.mk to go ahead and freshen up the whole NSS when it builds the client.
I'm not sure why'd you want to do that as only a specific static version of NSS is supported when building against the Mozilla trunk. You'd have to edit your client.mk and change the tag it uses to pull security/coreconf & security/nss.
I still haven't figured out your build process. For example, when I fetched NSS, it required me to have NSPR source there with it. Perhaps I could play with the include path to use the one I had already built. That doesn't bother me so much. What I would really like a better understanding of is the expectation implied by symlinking all the compiled binaries to dist rather than placing them there directly.
Symlinking is just to save space. Operating systems w/o symlink support (win32) copy the files there directly.
can't recall off the top of my head, but I had to do something like cp -rL * to get the actual files copied to where I wanted them. I assume NSS would be packaged for distribution using some additional script? Is that the same client.mk as I use to build the whole lizard?
Yes, a separate script is usually used to package builds. I don't know about the NSS packaging procedure but Mozilla uses the one outlined at http://www.mozilla.org/build/distribution.html .
And what about additional stuff such as Protozilla from mozdev.org. Should I be able to graft that onto my Mozilla CVS tree and expect the build process to simply pick it up?
That depends upon the instructions given by the mozdev project. Some use the Mozilla build system and can be added to mozilla/extensions and built when the build system is given the proper --enable-extensions argument. I don't know about the others.
- cls
