Yes, the '-L' option is very useful when you are compiling 'real'
win32-developed code that has just been checked out from a version control
system that is case insensitive for file names onto your disk published as
an SMB share.
Also, certain compiler suites seem to do case insensitive filename matching
by default, just for backward compatibility reasons AFAICT. :)
So, reworking the option to mean 'includes are case-insensitive' would
probably be a good idea. Do we have any volunteers?
Albert.
Francois Gouget wrote:
>
> On Mon, 11 Sep 2000, Jeremy White wrote:
>
> > In make_filename() converts the filename to lowercase,
> > with the comment:
> > /* Convert to lower case. Seems to be reasonable to do */
> >
> > And yet, it seems to me to be unreasonable to do so
> > (I have a case of including res/Toolbar.bmp that fails).
>
> I found a '-L' option that disables this behavior. I guess the idea
> would be to systematically use it as part of the wrc flags. I certainly
> do.
> Now, is this lowercasing functionality really needed in wrc?
> Especially in its current form: why should we suppose that the filename
> has been lowercased? I guess I would much prefer to see this as a
> 'includes are case-insensitive' option.
> So is it really needed? When wrc is used outside of Wine?
>
> --
> Francois Gouget [EMAIL PROTECTED] http://fgouget.free.fr/
> RFC 2549: ftp://ftp.isi.edu/in-notes/rfc2549.txt
> IP over Avian Carriers with Quality of Service
--
Albert den Haan, Lead Developer @ Linux Port Team . Corel Corporation
[EMAIL PROTECTED] x 5318
--
The address in the headers is not the poster's real email address. Do not send
private mail to the poster using your mailer's "reply" feature. CC's of mail
to mailing lists are OK. Problem reports to "[EMAIL PROTECTED]".
The poster's email address is "[EMAIL PROTECTED]".
