As Paul has been building the QT stuff he noted the OS/2 DLL name limitations.
This morning I was reading a security paper on Google One VPN and DLL redirection was highlighted as one of the findings (LOW impact).
Anyways, this remark was applicable to the Win binaries, but it did have a link to a MSDN article (
https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-redirection), so off I went reading wondering how Gates&Co solved this issue.
So while the redirection issue and the Win functionality to implement such a thing does not solve our problem, that made me think: so why not construct our very own re-direct DLL to help us deal with the existing limitations?
Basically a wrapper DLL.
Would it not be feasible to maintain a system-wide manifest that lists all installed DLLs, and for those that need to be longer than the 8 chars limitation we simply provide a virtual DLL name that the wrapper maps to and passes that onto the standard OS/2 DLL loader?
...or am I misunderstanding the nature of the OS/2 limitiation?