[Omake] "Strict" case sensitivity.

Aleksey Nogin nogin at metaprl.org
Mon May 14 11:59:07 PDT 2007


Jason,

I just came across one interesting implication of strictness. Imagine, 
you have a rule

foo: bar
   ...

in your OMakefile. Imagine you also have a "stale" file Foo left around 
on your filesystem (perhaps you used to have a case typo in your 
OMakefile). Well, depending on how the rule (and whatever tools it uses) 
happens to be, on a case-insensitive fs, it is quite likely that you 
would end up updating the "Foo" file and failing with the "rule failed 
to build target: foo" error...

Not sure what can be done about this. The only option (other than not 
doing anything at all) that I see is to check if the "wrong-cased" 
version of the target exists before the rule execution and rename it?

Also, one place where "strictness" might be a bit too dangerous is for 
locks/effects mutexes. Should we add code that uses canonical names for 
locks/effects?

Aleksey


More information about the OMake-Devel mailing list