Like, we probably wouldn't bother producing a custom build for ReactOS ourselves, especially since they are more than likely going to implement those features soon enough, but that said it probably wouldn't be that difficult to recompile a UXP application so that it looks for those functions elsewhere if you really wanted to.
https://learn.microsoft.com/en-us/windo ... srw--locks
Most of those functions are related to SRW locks, a key feature introduced in Vista, and mostly in Windows-specific code. The way we include them, is by including Windows.h header files. So all you would really need to do is either include a different header file instead of Windows.h in the places where we use those functions, or else use an alternate (ReactOS version) of Windows.h instead of the one Microsoft ships.
The issue is that ReactOS is likely trying to avoid using the Windows SDK, so none of the developers will want to look at this info or compile with Visual Studio against ReactOS headers for fear copyrighted code might sneak in.
EDIT: Though, if I understand the second thread correctly, recompiling apps to target ReactOS isn't the way they do things, and what you actually need to do to find a way to make the DLL exports work by messing with compatibility shims like they were talking about, or recompile ReactOS itself to target a newer version of Windows than the shipped build. The main problem is that ReactOS is targeting an older Windows API than what we support. We target NT6+, ReactOS is NT 5.2, which is too old. ReactOS has enough of NT6+ that it could theoretically run Pale Moon (possibly in a buggy fashion), but they turned it off for some reason.
"The Athenians, however, represent the unity of these opposites; in them, mind or spirit has emerged from the Theban subjectivity without losing itself in the Spartan objectivity of ethical life. With the Athenians, the rights of the State and of the individual found as perfect a union as was possible at all at the level of the Greek spirit." -- Hegel's philosophy of Mind
