Would someone please fill me in on direction for loader code?

Stefan Dösinger stefandoesinger at gmail.com
Wed Sep 2 06:04:24 CDT 2020



> Am 02.09.2020 um 13:29 schrieb Jefferson Carpenter <jeffersoncarpenter2 at gmail.com>:
> 
> What is the team's overall direction for that area of code?  Is it as simple as "it just has to work"?  Are there things about how it works that aren't expressed in code but have to be preserved?  Or do you have plans for how you're intending to change it in the future?

It is complicated and always evolving. The ntdll tests certainly capture a lot of requirements, but not everything. What's making matters more complicated is that DRM and anti-cheat systems hook into ever-lower levels of ntdll, and we have to do our best to replicate how things work on Windows.

What is it that you are trying to do in the loader code?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20200902/48020b94/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20200902/48020b94/attachment.sig>


More information about the wine-devel mailing list