[Omake] Another recursive omake question

[Benjamin Pierce]

I guess I invented a variant on your solution.  Looks like I'm  
getting the hang of things!  :-)

> Benjamin Pierce wrote:
>> Actually, I guess I see another way that is better than any of  
>> these:  in the OMakefile of the broken directory, change  
>> the .DEFAULT target  to DEFAULTBROKEN or something.  Now, when  
>> working there, we have to  remember to do "omake DEFAULTBROKEN",  
>> but this is perhaps not so bad...
>
> One style we often use is to use .DEFAULT only on the "most  
> important" thing we care about, so that running omake without  
> arguments does some minimal expected work.  All the other stuff is  
> put to a different target like "all" or "install".

But the problem will be the same whether the phony target is .DEFAULT  
or "all" or anything else: typing "make all" at top level will also  
attempt to make the broken one.  (I agree that your workarounds are  
at least somewhat reasonable, though...)

     - Benjamin


>
> Alternately, the -k or -P options tell omake to continue, even if  
> something is broken.  A list of broken targets is printed when  
> omake is done (though the error messages may have scrolled off the  
> screen!)  To minimize screen output, the -S and --progress options  
> help.  Typing these options each time can be clumsy, but you can  
> add them to the OMAKEFLAGS environment variable, or add a line like  
> this.
>
>    OMakeFlags(-S --progress)