[Omake] "Strict" case sensitivity.

Aleksey Nogin nogin at metaprl.org
Mon May 14 12:15:38 PDT 2007


On 11.05.2007 12:27, Jason Hickey wrote:

> Some questions are:
>    - What is the effect on performance?
>    - Should we be strict, or use the mixed style you proposed?

I am starting to think that strict will cause too many problems :-(

*** omake error:
    File lib\build\C.om: line 166, characters 1-38
    Do not know how to build "c:\Program Files\Microsoft Visual Studio 
.NET 2003\VC7\PlatformSDK\include\rpcdcep.h" required for 
"src\clib\lm_notify.obj"

(the real file name is RpcDceP.h, but the C scanner prints all the 
header files in lowercase).

> I think I prefer strict.  For the mixed style, there are two approaches,
>    1. Case-sensitive nodes, but canonical comparison (the style you had 
> before).

This is probably the way to go. Except, we might want to try adding some 
code to "inherit" the real case through the implicit rules.

>    2. Nodes are canonized, but they display using their realpath
> 
>       osh> X = $(file aBc)
>       Abc : File
>       osh> rm abc
>       osh> touch abC
>       osh> value $X
>       abC : File

The issue is that we'd also have to have the notion of a "realpath" for 
any "future" targets that we are planning to build in order for this to 
do what we want.

Aleksey



More information about the OMake-Devel mailing list