"David Bradley" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> What doesn't make sense to me is the list of unresolved externals. If
> something wasn't built I'd expect a file not found type error. But I'm
> still getting familiar with this build environment so someone else might
> recognize the symptoms and a solution.
To get this problem a new version of a file came down. But not everything
that depended on it got rebuilt. Some files got rebuilt and others didn't.
For example maybe the string lib files didn't get rebuilt but the xpcom com
clients that call the library did get built. Or the lib got rebuilt and the
dependency to copy it to the dist directory didn't trigger. Since the API
had changed there were link errors. String APIs can change without you
noticing because they are hidden behind macros. You don't get a file not
found because the old version of the lib was still there, it just didn't
export the new symbols.
It is also possible that not everyone sees the problem. For example another
h file could have changed an hour after I updated which could have caused
the files in question to build. People updating later would receive both
changes and never notice the dependency problem from the first one.
This is a common problem with build systems that require manual updates of
dependencies.
--
Jon Smirl
[EMAIL PROTECTED]
