[Omake] Dependency scanning problem (default scanners)

Jonathan Roewen jonathan.roewen at gmail.com
Sun Apr 8 15:44:57 PDT 2007


Hi,

I seem to have found a bug in dependency scanning... =/

start_scanner: target dependencies are accurate <scanner
kernel/bytecomp/scan-ocaml-lambda.mli>:
   scanner's build deps: <phony <OCamlGeneratedFilesTarget>>
      kernel/bytecomp/lambda.mli
   scanned deps:
      kernel/lambda.cmi: parsing/asttypes.cmi parsing/location.cmi
         stdlib/set.cmi typing/env.cmi typing/ident.cmi typing/path.cmi
         typing/primitive.cmi typing/types.cmi
finish_scanner <scanner kernel/bytecomp/scan-ocaml-lambda.mli>:
   kernel/lambda.cmi: parsing/asttypes.cmi parsing/location.cmi
      stdlib/set.cmi typing/env.cmi typing/ident.cmi typing/path.cmi
      typing/primitive.cmi typing/types.cmi
- build kernel/bytecomp lambda.cmi
+ ../../toolchain/ocaml/ocamlc -nostdlib -I . -I ../utils -I
../parsing -I ../typing -I . -I ../driver -I ../stdlib -c lambda.mli
File "lambda.mli", line 17, characters 0-13:
Unbound module Asttypes

As you can see in scanned deps: it's putting the dependencies on
kernel/lambda.cmi. The correct target is kernel/bytecomp/lambda.cmi =/

I'vel attach my OMakefile for completeness.

bytecomp/Files.om:

COMP = $(file lambda printlambda typeopt switch matching \
	translobj translcore translclass translmod simplif runtimedef)

BYTECOMP = $(file meta instruct bytegen printinstr opcodes \
	emitcode bytesections dll symtable bytelink bytelibrarian \
	bytepackager)

Note that other files get scanned fine up to that point.

Using omake 0.9.8.1

Jonathan


More information about the Omake mailing list