> Date: Fri, 18 Jul 2003 10:58:19 -0700 (PDT) > > > I am in the process of specifiying our build process > and was wondering what some other folks do. > > Do any of you check in build results (binaries, libs, > etc) of a completed build in with the codebase? We > currently label the codebase with a build number > before we do the build so we have the ability to > reproduce that exact build. > > This question comes up because we are trying to > determine how to handle dependencies in the build > process. For example, component A depends upon > component B which depends upon component C. There are > various ways to handle this, checking in build results > being only one of them. I was wondering if anyone > might have some advice to offer.

I don't recommend checking in build results unless the results are pretty static.

Once you start checking in build results, (that are not very static), you have to start using tempobj or the equivalent, which brings its own set of problems.

We found the complications of this approach much more profound than we ever expected, and they are non-obvious.

A simple one might be reproducing an old build. Unless you have it on its own branch, and nothing else happened on the branch, then the build results will get reverted to the old build versions. If developers actually *use* the build results, you have just reverted all of their environments the next time they sync.

There are ways to get around the problems, but they get more and more ugly.

dave