Signed-off-by: Serge Gautherie winehq-git_serge_180711@gautherie.fr --- See https://testbot.winehq.org/JobDetails.pl?Key=71897 --- .../api-ms-win-downlevel-shell32-l1-1-0.spec | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dlls/api-ms-win-downlevel-shell32-l1-1-0/api-ms-win-downlevel-shell32-l1-1-0.spec b/dlls/api-ms-win-downlevel-shell32-l1-1-0/api-ms-win-downlevel-shell32-l1-1-0.spec index 9d03c03..72e51bc 100644 --- a/dlls/api-ms-win-downlevel-shell32-l1-1-0/api-ms-win-downlevel-shell32-l1-1-0.spec +++ b/dlls/api-ms-win-downlevel-shell32-l1-1-0/api-ms-win-downlevel-shell32-l1-1-0.spec @@ -1,3 +1,3 @@ -@ stdcall CommandLineToArgvW(wstr ptr) shell32.CommandLineToArgvW -@ stdcall GetCurrentProcessExplicitAppUserModelID(ptr) shell32.GetCurrentProcessExplicitAppUserModelID -@ stdcall SetCurrentProcessExplicitAppUserModelID(wstr) shell32.SetCurrentProcessExplicitAppUserModelID +@ stdcall -arch=win32 CommandLineToArgvW(wstr ptr) shell32.CommandLineToArgvW +@ stdcall -arch=win32 GetCurrentProcessExplicitAppUserModelID(ptr) shell32.GetCurrentProcessExplicitAppUserModelID +@ stdcall -arch=win32 SetCurrentProcessExplicitAppUserModelID(wstr) shell32.SetCurrentProcessExplicitAppUserModelID
Could it mean that physical files for this were removed at some point, but loader still is able to resolves imports on 64-bit too?
On 19/05/2020 15:42, Nikolay Sivov wrote:
Could it mean that physical files for this were removed at some point, but loader still is able to resolves imports on 64-bit too?
I don't know. Maybe François can check/answer that. In any case, either code or testbots don't match...
On Tue, 19 May 2020, Serge Gautherie wrote:
On 19/05/2020 15:42, Nikolay Sivov wrote:
Could it mean that physical files for this were removed at some point, but loader still is able to resolves imports on 64-bit too?
I don't know. Maybe François can check/answer that. In any case, either code or testbots don't match...
I have never removed dlls from the Windows test VMs (and would never do such a thing). Does that answer the question?
On 6/1/20 12:49 PM, Francois Gouget wrote:
On Tue, 19 May 2020, Serge Gautherie wrote:
On 19/05/2020 15:42, Nikolay Sivov wrote:
Could it mean that physical files for this were removed at some point, but loader still is able to resolves imports on 64-bit too?
I don't know. Maybe François can check/answer that. In any case, either code or testbots don't match...
I have never removed dlls from the Windows test VMs (and would never do such a thing). Does that answer the question?
I meant removed by Windows update obviously, not by hand.
On Mon, 1 Jun 2020, Nikolay Sivov wrote:
On 6/1/20 12:49 PM, Francois Gouget wrote:
On Tue, 19 May 2020, Serge Gautherie wrote:
On 19/05/2020 15:42, Nikolay Sivov wrote:
Could it mean that physical files for this were removed at some point, but loader still is able to resolves imports on 64-bit too?
I don't know. Maybe François can check/answer that. In any case, either code or testbots don't match...
I have never removed dlls from the Windows test VMs (and would never do such a thing). Does that answer the question?
I meant removed by Windows update obviously, not by hand.
Wouldn't the error happen in w1064v1607 or later but not on the original w1064v1507 snapshot then?
Similarly w2008s64 gets the same error so that would mean I should find a file called api-ms-win-downlevel-* or api-*shell32* on the original snapshot of w2008s64 which is not the case.
Let me know if there are other tests I can do to help.
On 5/19/20 18:22, Serge Gautherie wrote:
On 19/05/2020 15:42, Nikolay Sivov wrote:
Could it mean that physical files for this were removed at some point, but loader still is able to resolves imports on 64-bit too?
I don't know. Maybe François can check/answer that. In any case, either code or testbots don't match...
As I understand api-...dll's do not necessarily need to be physically present to be "loaded" on Windows, these are virtual libraries (see, e. g., [1], [2], [3]).
1. https://blog.quarkslab.com/runtime-dll-name-resolution-apisetschema-part-i.h...
2. https://docs.microsoft.com/en-us/windows/win32/apiindex/windows-apisets