Comments on: It’s CLOBBERin’ time! http://antennasoft.net/robcee/2007/03/28/its-clobberin-time/ more than just sandwiches Wed, 28 Mar 2012 15:43:45 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: robcee http://antennasoft.net/robcee/2007/03/28/its-clobberin-time/comment-page-1/#comment-2998 robcee Thu, 29 Mar 2007 01:58:51 +0000 http://antennasoft.net/robcee/2007/03/28/its-clobberin-time/#comment-2998 Yeah, that was a mistake on my part, David. I'll post a correction here as well just in case... the correct path is mozilla/<strong>tools</strong>/tinderbox-configs/... Good point, Brendan. Recently most of the requirements for the clobbers I've seen have been because tests have gotten moved around and the _tests directory under objdir needed to be wiped out. Overall, I'd say the build system is holding up pretty well. Yeah, that was a mistake on my part, David. I’ll post a correction here as well just in case…

the correct path is mozilla/tools/tinderbox-configs/…

Good point, Brendan. Recently most of the requirements for the clobbers I’ve seen have been because tests have gotten moved around and the _tests directory under objdir needed to be wiped out. Overall, I’d say the build system is holding up pretty well.

]]> By: David Baron http://antennasoft.net/robcee/2007/03/28/its-clobberin-time/comment-page-1/#comment-2979 David Baron Thu, 29 Mar 2007 00:12:08 +0000 http://antennasoft.net/robcee/2007/03/28/its-clobberin-time/#comment-2979 I don't see a mozilla/testing/tinderbox-configs/ directory in CVS. I don’t see a mozilla/testing/tinderbox-configs/ directory in CVS.

]]> By: Brendan Eich http://antennasoft.net/robcee/2007/03/28/its-clobberin-time/comment-page-1/#comment-2974 Brendan Eich Wed, 28 Mar 2007 23:38:18 +0000 http://antennasoft.net/robcee/2007/03/28/its-clobberin-time/#comment-2974 I'm sure Benjamin will keep after this general issue, but I wanted to point it out here in case others can help: If we find the build system failed to handle dependencies of some kind, and we had to force a clobber, we should push on the issue of whether the build system *could* be fixed or extended to track the missed dependency. It often can't be done, or it could be prohibitively expensive. But it's worth asking now and then, or quickly each time, to avoid missing an opportunity for more complete automatic build dependency inference. /be I’m sure Benjamin will keep after this general issue, but I wanted to point it out here in case others can help:

If we find the build system failed to handle dependencies of some kind, and we had to force a clobber, we should push on the issue of whether the build system *could* be fixed or extended to track the missed dependency.

It often can’t be done, or it could be prohibitively expensive. But it’s worth asking now and then, or quickly each time, to avoid missing an opportunity for more complete automatic build dependency inference.

/be

]]>