oblem with the scheme was that each <CODE>make</CODE> process had a
separate configuration, and it took a lot of work to make sure that everything was consistent.
Furthermore, suppose the programmer runs <CODE>make</CODE> in the <CODE>main/</CODE> directory, but the
<CODE>lib/</CODE> is out-of-date. In this case, <CODE>make</CODE> would happily crank away, perhaps trying to
rebuild files in <CODE>lib/</CODE>, perhaps just giving up.</P><P>With OMake this changes entirely. Well, not entirely. The source stru