Closed borg323 closed 3 years ago
Thanks, but I'm going to pass on this - Windows Frotz doesn't usually see that much development these days, so I don't think it's really worth it.
This is fine, but note that this branch has two patches that may be of interest:
On the patches:
The only reason I used the latest libjpeg version is that 6b has a typedef for INT32
that is incompatible with a microsoft header definition. I can just use sed
to change it, or maybe define somewhere XMD_H
which avoids the offending typedef but is a bit messy. Using libjpeg-turbo is also an option as it handles this better: https://github.com/libjpeg-turbo/libjpeg-turbo/blob/master/jmorecfg.h#L175
Just noticed that using libjpeg 6b was an explicit decision (commit https://github.com/DavidKinder/Windows-Frotz/commit/c03ea408708bdb6a5e2c596f4a93f866f7f84b5d). I'll work around the INT32
issue another way.
Closing as Windows Frotz is now built with Visual Studio 2019.
I don't know if this is of interest, but I managed to get Windows-Frotz building under appveyor. You can see the details in https://github.com/borg323/Windows-Frotz/tree/appveyor.