On December 9, 2002 04:57 pm, Francois Gouget wrote:
I agree with that one. As it is wrc just convert the filenames to
lowercase before trying to include them which is just plain wrong. In
particular it causes compilation errors if the file really has a
mized-case which is not that uncommon.
On Sun, 8 Dec 2002, Dimitrie O. Paun wrote:
[...]
-L Leave case of embedded filenames as is\n
Shouldn't this one be on by default? Why do we need this option?
I agree with that one. As it is wrc just convert the filenames to
lowercase before trying to include them which is
Hello people,
I was looking at wrc a little bit, and I am curious to know if
we really need all these options. They just pollute the command line
namespace, and add confusion. windres has none of these options,
and it's doing just fine.
Let me be more explicit:
-a nAlignment
-B xSet output byte-order x={n[ative], l[ittle], b[ig]}\n
(win32 only; default is n[ative] which equals
Again, shouldn't this be hardcoded to some standard value, that we
expect in Wine when we read the resources?
The CPU byte-order is needed
Dimitrie O. Paun [EMAIL PROTECTED] writes:
I was looking at wrc a little bit, and I am curious to know if
we really need all these options. They just pollute the command line
namespace, and add confusion. windres has none of these options,
and it's doing just fine.
wrc does a lot more than
On December 8, 2002 05:57 pm, Alexandre Julliard wrote:
wrc does a lot more than windres. We don't use all the features in the
Wine building process but that's not a reason for removing them.
I know that wrc does more than windres. I was just asking if some of
these options are superfluous. In
Dimitrie O. Paun [EMAIL PROTECTED] writes:
I know that wrc does more than windres. I was just asking if some of
these options are superfluous. In particular, do we need to support
win16 resources?
Yes we do, some of our 16-bit dlls have resources.
--
Alexandre Julliard
[EMAIL PROTECTED]
