The original cvtres.exe sets the high bit when an identifier offset
points to a string. Even though this is not mentioned in the spec, and
in fact does not seem to cause errors with most cases, for some reason
this causes a failure in Chromium where the new resource file is not
verified as a new version. This patch sets this high bit flag, and also
adds a test case to check that the output of our library is always
identical to original cvtres.
Details
Details
Diff Detail
Diff Detail
- Build Status
Buildable 8031 Build 8031: arc lint + arc unit
Event Timeline
Comment Actions
Does this mean that the output of your cvtres is exactly bit-wise the same as Microsoft's?