I *thought* I had fixed the multiple-build problem (i.e. make followed by a make shouldn't rebuild everything when nothing has changed). It worked last week, anyway.
I'm guessing that I inadvertently broke it when I moved the files around. I've submitted another fix to CVS. This one should work (*crosses fingers*). If you still have a problem after a CVS update, let me know. Thanks, - Jon On Wed, 2003-01-15 at 23:06, Nick Drochak wrote: > | I feel like we're discussing solutions to a problem which isn't entirely > | solvable. (At least, not solvable without the presence of autoconf > | scripts and similar mechanisms.) > > Fine. I just want the build to go faster. Every time I do a 'make test' I > have to wait for type-reflector to do it's thing. > > | I don't fully understand one of your statements, when you say: "Should > | the third attempt not build a second time if it succeeded the first > | time?" > | > | If I understand you correctly, then you're asking for the current > | behavior. If it builds console-only output the first time, and then you > | rebuild (without an intervening clean), then it shouldn't be rebuilt. > | (Unless the type-reflector source has been updated in CVS, which would > | cause a full rebuild of type-reflector, resulting in three compiles, > | assuming the build machine hasn't changed.) > > It always tries three times, and the first two fail (as they should) and the > third re-compiles everything, even though no sources have changed each time > I do a 'make'. > > Nick D. > _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
