On Thu, Jun 26, 2008 at 10:31 PM, troy d. straszheim <[EMAIL PROTECTED]> wrote:
> David Abrahams wrote: > >> troy d straszheim wrote: >> >> Things look good. So... Dave is it possible you were doing >>> configuration of cmake in a build directory that had failed >>> configuration once? >>> >> >> Gosh, I don't know. Maybe. Probably. Heck, shouldn't that work, after >> all!? How will our users survive if one failure torpedoes all further >> attempts? >> >> > It is just a standard cmake gotcha: configuration/generation fails, the > cache isn't deleted, and whatever it was that caused the failure is > preserved in the cache to fail on the next attempt. You can reduce this > effect by being careful what you cache, but in this case, well, we're still > just hackin' on this thing.... I thought cmake was supposed to be robust. This is very discouraging; it implies cmake developers are only targeting folks who are cmake experts. Is it possible to disable this misfeature? --Beman
_______________________________________________ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
