jsiwek at ncsa.illinois.edu
Mon Jan 24 08:57:20 PST 2011
> > Could the configure wrapper just decline to configure with a
> > different set of options than last time (plus some advice on how to
> > solve the problem)? Now that we have config.status, we already
> > remember what was used before.
> I was also thinking this approach would be good. I'll wait to see if
> there's more comments, though.
Thought of solution that I think is best: on each invocation, the configure wrapper can just delete an existing CMakeCache.txt before calling cmake (no need for displaying warnings to user about anything).
This makes each ./configure independent from previous ones.
More information about the bro-dev