Reply To: MWEdit

Yet another thing to add to the investigation list! Yeah, we may want to swap out that macro with something more modern. There have been a lot of updates to pointer support in recent years 🙂

The debug settings are complaining about missing libraries such as winsock when release does not so I’m going ahead and removing the PCH support to help us sort through everything. Needs to be done anyways and it’ll help us diagnose what’s needed where. This is going to take some more time, it looks like, to untangle the Windows library stuff. This means I’m going to have to remove the mwedit/std_afx.h include from all of the files, which will take another week or so. *sigh* It’s probably as good a time as any.

Er never mind. I just realized that’ll break MFC support. Reverting now….

Will need to keep at it for a while. The MFC headers need to be added to the GUI files before we can remove PCH support. I hope I’m not breaking too much here…. I should probably check the commit log before I do anything more to make sure release would still function

Okay, now we’re back to it complaining about winsock even though we’re not using network code. Weird. Will set it aside for now and take a look another day. Don’t know why turning on debug builds meant trying to use winsock. Here’s the current build log if you want to take a looksie: https://github.com/Walrus-Tech/MWEdit/actions/runs/21025793442/job/60449870823

Did some looking at it appears that winsock is brought in regardless and not all of the MFC includes have been updated to use winsock2. Weird. May or may not be easy to fix.