The files in mozilla/dbm are part of NSS, or are at least only used by NSS. However, they are not built as part of the NSS build system but rather the mozilla build system. There is also mozilla/security/dbm (I can't figure out if anyone uses this code) and mozilla/security/nss/lib/ckfw/dbm, which appears to be built when NSS is built outside of Mozilla. I think that the easiest solution here is to have NSS always use mozilla/security/nss/lib/ckfw/dbm and to stop building mozilla/dbm altogether.
mozilla/security/dbm is a set of makefiles that build dbm from the sources in mozilla/dbm/src, when dbm is being built outside of mozilla (e.g. a pure NSS build). NSS builds always build dbm using the makefiles in mozilla/security/dbm. It's not broken now, and I don't think we should "fix" it now. Our present NSS build processes depend on things being as they are. Changing them now seems like more work with little immediate benefit. The stuff in security/nss/lib/ckfw/dbm is not presently used in existing NSS releases, AFAIK. It is future work in progress, eventually to replace the older dbm code, IINM. But it will be some time before the new DBM replacement is ready, or perhaps I should say, before NSS is ready to use the new replacement DBM.
What I want is for the mozilla client NSS build system to build DBM the same way the standalone NSS system does it (using the makefiles in mozilla/security/dbm, from your comment). I have particular requirements for cleaning out mozilla builds so that $(DIST)/lib doesn't contain the intermediate static libraries, and general requirements for decoupling the NSS and mozclient build processes as much as possible.
Ben, bug 301249 has the proposed solutions and describes the major challenge that mozilla/dbm is part of the SeaMonkeyAll CVS module. *** This bug has been marked as a duplicate of 301249 ***
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Component: Build → Build Config
Product: NSS → Core
Resolution: --- → DUPLICATE
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.