wine

https://github.com/wine-mirror/wine/blob/master/loader/main.... According to WINE itself, WINE is an emulator. Ultimately there's a spectrum between emulation and native code and where you draw the line is an arbitrary and subjective choice.

This isn't really my arena, but I did happen to recently compare the implementation of ReactOS's RTL (Run Time Library) path routines [0] with Wine's implementation [1]. ReactOS covers a lot more of the Windows API than Wine does (3x the line count and defines a lot more routines like 'RtlDoesFileExists_UstrEx'). Now, this is not supposed to be a public API and should only be used by Windows internally, as I understand it. But it is an example of where ReactOS covers a lot more API than Wine does or probably ever will, by design. To whom (if anyone) this matters, I'm not sure. [0] https://github.com/reactos/reactos/blob/master/sdk/lib/rtl/p... [1] https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/p...

My favorite piece of trivia is that main.c of the wine loader actually calls itself "emulator initialisation code" :D https://github.com/wine-mirror/wine/blob/master/loader/main....

No this is untrue. Independent creation is an affirmative defense against copyright infringement. You'd never convince a jury that you independently wrote the exact same article as a New York Times article, but in principle you can argue that you independently wrote say... a song, or even reimplemented the WIN32 API without ever having read or familiarized yourself with the original source code: https://github.com/wine-mirror/wine https://harvardlawreview.org/print/vol-128/creating-around-c...

Correct - the instructions in the Windows PE executable run natively. WINE provides a PE loader for exe and dll files (https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/l...) and provides its own version of the API (user32.dll, kernel32.dll etc)

Wine has a similar problem around needing to reserve the lower 32 bit address space for 32-bit executables. I bookmarked their Mac workaround around here: https://github.com/wine-mirror/wine/blob/b2a099b3ceec6fef05c... which involves rearranging the zero page and creating a big WINE_RESERVE section. On Linux it appears they use a -Ttext linker flag to reposition the code location, but I haven't read it too carefully: https://github.com/wine-mirror/wine/blob/b2a099b3ceec6fef05c...

Sometimes when a detail of Windows isn't documented, the Wine source code can be useful. Have you tried looking at it for details of win64 SEH? For example: https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/e... https://github.com/wine-mirror/wine/blob/master/dlls/msvcrt/...

Source code: https://github.com/wine-mirror/wine/tree/master/programs/wor...

It's Wine with some special sauce (Apple couldn't reuse VKD3D because they chose to invent Metal rather than stick with OpenGL/Vulkan so they had to build their graphics translation themselves). Crossover is built on the same technology. In fact, Apple's brew script literally links to Crossover's sources: https://raw.githubusercontent.com/apple/homebrew-apple/main/... Things like the crypto API should be implemented if you can find the reference for your specific API calls here: https://github.com/wine-mirror/wine/tree/master/dlls/crypt32 Apple's version of Wine is aimed at developers, though. It shouldn't take too long for someone to make an app or script to easily set up environments with the developer runtime, but I doubt they'll support it as well as Valve supports Proton. If your application of choice doesn't need any fancy graphics,

Not the OP, but Github's stats on https://github.com/wine-mirror/wine say the current Wine codebase is 95.1% C, 0.3% C++

Take a look at Wine's commit log. It's really well curated. https://github.com/wine-mirror/wine/commits/master

The processor itself supports configuring some aspects of floating point behavior; on x86 this is the MXCSR register. The most important one is rounding mode: you can choose round-to-nearest, round-down, round-up, or round-towards-zero. Less common options include whether to raise an exception on various out-of-range conditions, and whether to treat denormal numbers as zero (faster but less accurate and not IEEE 754 compliant). The C standard library has functions to do this configuration; search for fesetenv. _fpreset is not a standard function but, at least in Wine's implementation [1], just resets the relevant configuration registers to an initial state. [1] https://github.com/wine-mirror/wine/blob/e909986e6ea5ecd49b2...

> PM from GitHub here Hey totally off topic sorry. Can you get someone to turn off pull-requests for the unofficial mirrors that you guys created for some open source projects? Users are being mislead into thinking opening PRs there is productive, but they're not monitored by our project and we don't own the repo anyway. https://github.com/wine-mirror/wine/pulls I've tried contacting your support, but they just tell me that they don't own the repo, which is obviously false[1]. I don't know who to reach out to. [1] https://github.community/t/how-is-the-mirrored-from-annotati...

Indeed. Even with some versioning schemes where 4.2 would equal 4.20 I wouldn't see the point in changing the title from what the project itself used. And if I'm reading this[1] correctly, the versions look pretty straightforward (i.e. 4.1 < 4.10 etc.). [1] https://github.com/wine-mirror/wine/commits/master/VERSION

> But the answer is because GitHub doesn't distinguish what is and isn't a mirror They do. See the "mirrored from" text near the top of the page. These unmaintained mirrors, which GitHub created and no one owns, just collected PRs from well-intentioned users, and it's up to random other people or the maintainers of the project to go tell them how to submit properly. I've emailed GitHub support about this, as it hits the Wine project, too[1], but they refuse to do anything. It feels like a dark pattern, to try to make GitHub the one-and-only source for open source projects. One of several reasons I dislike GitHub and wish it wasn't so well embraced by the open source community. [1] https://github.com/wine-mirror/wine/pulls