[Omake] scanning of .mly files

[Aleksey Nogin]

On 12.06.2006 13:01, Jason Hickey wrote:

> Christian Stork wrote:
> 
>> Intuitiely, it would seem that the only reasonable solution to this
>> problem is some kind of build stage concept (a generaliztion of
>> OCamlGeneratedFiles)
> 
> 
> I had been thinking along these lines too.  I worry that it is 
> complicated.  OTOH, we could probably define it so normally you wouldn't 
> see it.
[...]
> I do prefer fixing ocamldep, but on the other hand, this issue may come 
> up in other languages too.

I strongly agree that this should be fixed by fixing the scanners (even 
if we end up having to reimplement an internal ocamldep :-( ). The 
"staging" idea seems to go against the whole ideology of OMake - in 
OMake there are no "stages", the whole project is one big thing, where 
the dependencies specify the build order (and in fact over time, we 
moved from the implementation where scanning was a special stage during 
a build cycle for a specific target to where scanner targets are more 
similar to regular ones and no longer implemented as a special "stage").

The "stage" idea gives me the feeling of "recursive make" style (in 
make, the recursive calls are often used for "staging"), which is 
something that we are trying hard to get away from...

OTOH, staging can be easily done using the .PHONY targets (this is what 
the OCamlGeneratedFiles used), so it is not clear whether adding special 
syntax is warranted here.

-- 
Aleksey Nogin

Home Page: http://nogin.org/
E-Mail: nogin at cs.caltech.edu (office), aleksey at nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200