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? 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 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. I 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?
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?
STH
