-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows support #1
Comments
(comment copied from GitLab, dates are incorrect) There are still a whole bunch of issues, but (for now), I've lost the desire to fix them.
Even if we get past those issues in a reasonable way:
All-in-all, it's looking like Windows is shaping up to very much be the "wild west" in terms of API. The core works fine and is completely cross-platform, but interfacing with the Windows server is proving difficult. |
(comment copied from GitLab, dates are incorrect) Going to do a little more work on this. Not windows support directly, but:
This removes the need for the weird macros scattered throughout the code. All you need to do is, RequestExclusiveHook<address, CallingConvention::ThisCall>, and magic happens automatically. |
(comment copied from GitLab, dates are incorrect) I've done this now, so now all the ugly cross-platform hook landing macros are contained within HooksImpl.hpp. I'm going to drop this task as being assigned to me for now. I'm still going to code with both platforms in mind but I'm not going to actively develop for Windows until all of the high priority stuff is out of the way (plugins, Arelith-specific stuff, etc). |
Aaand ... we're back in present time. Windows support depends on four things:
See https://github.com/nwnxee/unified-apigen for progress on 1, 2, and 3. |
Bring nwnx64 up to date
Closing this as WNF. We'll support running on Windows via docker or via WSL/WSL2. We won't support the nwserver.exe binary though. (building on windows is also a possibility, but a separate issue altogether) |
ObjectEvents.cpp to support OBJECT_USE BEFORE/AFTER
We need support for Windows.
The text was updated successfully, but these errors were encountered: