On Tue, 14 Feb 2017 14:36:36 +0100, Alexandre Julliard wrote:
Akihiro Sagawa sagawa.aki@gmail.com writes:
On Tue, 14 Feb 2017 10:18:51 +0100, Alexandre Julliard wrote:
Akihiro Sagawa sagawa.aki@gmail.com writes:
@@ -1078,6 +1086,67 @@ BOOL WINAPI VerQueryValueW( LPCVOID pBlock, LPCWSTR lpSubBlock,
(snip)
- static const WCHAR wineW[] = {'W','i','n','e', 0};
- static const WCHAR kernel32W[] = {'k','e','r','n','e','l','3','2','.','d','l','l',0};
That's very hackish, we need a more general solution.
How about introducing target DLL list in the registry, as seen in DLL overrides? Or, do you mean MUI files, like kernel32.dll.mui?
They should be normal resources, there shouldn't be any need to modify them after loading. We probably don't need separate MUI files, so the resources can all be in the main file, just like we do for other resource types.
Thanks for your comments. I'll attempt to define multiple version resources in the single file.
Akihiro Sagawa