[Omake] More on ocamldep and generated files.

Jason Hickey jyh at cs.caltech.edu
Mon Jun 12 21:51:53 PDT 2006


Aleksey Nogin wrote:
> So my proposal would be to:
> 1) Lobby OCaml maintainers to add a "-modules" flag that would cause
> ocamldep to forgo the second step, simply printing out the list of modules.

I like the idea.  If we are to lobby successfully, we need a patch. 
I've attached one below.  When given the -modules flag, this ocamldep 
produces output in human-readable, yet unambiguous form.  Modifications 
welcome.

I am still in favor of an augmenting the rule function.  While you might 
not like staging, you should at least be able to do it.  Proposal: add 
RULETARGETS and RULEDEPS variables.

This input:

     targets: deps
         commands

really means this:

     targets: deps
         commands
     $(RULETARGETS): targets    # If RULETARGETS is defined and non-empty
     targets: $(RULEDEPS)       # If RULEDEPS is defined and non-empty

This scheme can for example 1) deprecate OCamlGeneratedFiles (yay!), 2) 
also solve the generation hierarchy (foo.mly generated by OCamlProgram 
bar, generated by OCamlProgram baz, etc.).

However, before going this direction, I must understand the Menhir build 
first.

Jason

-- 
Jason Hickey                  http://www.cs.caltech.edu/~jyh
Caltech Computer Science      Tel: 626-395-6568 FAX: 626-792-4257
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ocamldep.patch
Type: text/x-patch
Size: 2766 bytes
Desc: not available
Url : http://lists.metaprl.org/pipermail/omake/attachments/20060612/51992f32/ocamldep.bin


More information about the Omake mailing list