On Tue, 9 Jun 2020, Steve Lhomme wrote:
On 2020-06-09 10:41, Martin Storsjö wrote:
On Tue, 9 Jun 2020, Steve Lhomme wrote:
The functions in winstorecompat cannot be linked properly when
cryptoapi-l1-1-0
is linked at the same time.
Can you give a more technical explanation on this part? If symbols are
available in both, and winstorecompat is linked before cryptoapi-l1-1-0,
then it should always prefer the ones from winstorecompat, right? (At
least with how lld links things.)
Yes. I changed the order of my libs and that solved the double linking
issue. So we could do without this patch.
Ah, ok, that clarifies it.
But in the end I think it's wrong to force users to link to keep
forbidden API's in libwindowsapp.a in general.
Sure, I'm ok with this change as such. (Contrary to the case with UCRT,
there's less reason to want to link against this import library while
targeting a regular non-UWP-restricted app.)
When used with mincore the only way to link these calls was through
winstorecompat so builds from be affected by this change.
^ this is missing a negation and the sentence isn't really parseable
around "builds from be"
s/from/won't/
Ok, that makes it understandable :-)
// Martin
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
