Neil wrote, On 2008-02-23 15:34: > Nelson Bolyard wrote: > >> Neil, here's what I find strange about all this. >> >> The code you cite builds and runs, without error, continuously, on a >> whole bunch of tinderbox systems >> > That's because a number of factors are required to trigger this "bug": > > 1. The bug does not affect clobber builds, because > dist/public/nss/pkixt.h is deleted by definition > 2. The bug does not affect systems that support symlinks, because > dist/public/nss/pkixt.h is simply a reference to the real pkixt.h, > and so never goes out of date, and therefore it doesn't matter > which pkixt.h the compiler uses. > > However with Windows depend builds, such as mine or tpol (see my other > post regarding tpol), dist/public/nss/pkixt.h is stale, and causes the > compilation errors. > > What does the NSS build system do to prevent stale headers from > polluting dist/public/nss?
Ah, well, presently, NSS doesn't fully support depend builds on Windows. We don't have a tool for generating dependency files on Windows. Years ago, we had a tool for generating dependency files on Windows, but there were licensing issues with it (IIRC), and so when we finally were able to open source NSS, we dropped that tool. Consequently, today we recommend clobber builds for NSS on Windows. That's not a big burden if you're building NSS by itself. It's potentially more of a burden if you're building NSS as part of a larger project. I suppose it could be fixed by a change to the Mozilla wrapper makefile for NSS, a change that made it clobber NSS for certain targets. I'd like to get a dependency tools for Windows again. I guess there's one as part of Mozilla, but I don't want to have to build the whole browser to get a dependency tool. _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
