On Wed Oct 26 18:50:23 2022 +0000, Konstantin Kharlamov wrote:
So, I tweaked it locally to say a:
Library lib2.dll (which is needed by L"Z:\tmp\foo\lib1.dll") not
found or has dependency missing and asked `<tinwhiskers>` on IRC would that unveil the problem. They say:
That's not ideal as you'll still likely have to go on the wild goose
chase to confirm the file is actually there. Indeed, now that I think of that, such formulation doesn't clarify which dll wasn't found. I imagine that might be a problem if there's many paths where a dlls for the application may be located, so you have to check all of them for each dll. I don't know, it seems to me, like adding an optional parameter `BOOL *err_for_parent_dll` might be better for end-users. What do you think?
Alright, well, maybe: `Library lib2.dll (which is needed by L"Z:\tmp\foo\lib1.dll") or a library it depends upon not found`? Though a bit longer than a `…or has dependency missing`, but a "missing dependency" sounds a bit too abstract. I see no better wording.