Re: OpenMW 0.45.0
Posted: 20 Oct 2018, 03:52
Haha, well that's what happens when someone who writes the code does the changelog I guess.
Weird. It this period there were a lot of CI and dependency changes.terabyte25 wrote: ↑20 Oct 2018, 03:30 Okay, so I tried looking for when this appeared, and it appeared all the way back in late June. It started when macOS support was broken (OpenMW client didn't launch) June 20th(OpenMW-20062018-22eb037) all the way to June 28th(OpenMW-28062018-f07d50e). I believe it was the either the commit that broke macOS support, or the commit that fixed macOS support that caused this regression to pop up.
What would be the best commit to check first?akortunov wrote: ↑23 Oct 2018, 20:15Weird. It this period there were a lot of CI and dependency changes.terabyte25 wrote: ↑20 Oct 2018, 03:30 Okay, so I tried looking for when this appeared, and it appeared all the way back in late June. It started when macOS support was broken (OpenMW client didn't launch) June 20th(OpenMW-20062018-22eb037) all the way to June 28th(OpenMW-28062018-f07d50e). I believe it was the either the commit that broke macOS support, or the commit that fixed macOS support that caused this regression to pop up.
For example, we started to use the 10.13 SDK for Mac OS.
I suppose we need an actual bisect to find out what exactly causes the issue.