On Wed, 6 Apr 2022, Jeremy Drake via Mingw-w64-public wrote:

> I was looking into adding the 'new' dloadhelper.lib (Windows 8+,
> required to be used for UWP apps) to mingw-w64.

> It seems what *should* be in libdelayimp.a is actually
> in libmingwex.a.  Is this intentional?  Will this cause me issues if I try
> to create and use libdloadhelper.a which contains an alternate
> implementation of __delayLoadHelper2 and __HrLoadAllImportsForDll?

After doing some searching of the archives, it seems that the delayimp
objects being in libmingwex rather than libdelayimp is known and was
discussed as recently as April 2020.  And doing a quick test with
clang/lld linking in the dloadhelper.lib from the Windows SDK didn't cause
any duplicate symbol errors, and used the implementation from
dloadhelper.lib instead of the delayimp implementation from libmingwex.
So I don't think that the current state of affairs should interfere with
what I was going to try to do.


_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to