![]() In the case of Mac OS X binaries, we do not have a Mac OS X system. That drastically reduces the chance of errors slipping through. Normally, a dev will test whether a change works at his own system before publishing the change. In principle, any change that we make in the OpenTTD source code or in the way we compile the program, may break the program. ![]() The second problem is building of the Mac OS X binaries. They just sit in Flyspray (our bug tracker) without any hope of getting fixed. Also, we have not found a Mac OS X 10.6 user capable enough to continue the porting and keep the Mac OS X port alive.Īs a result, all the Mac OS X issues are not being fixed. Unfortunately, currently we do not have such a person. The new bugs would not be a problem if we had an active porter that works on those issues and fixes them. For both of them we have no satisfactory solution. Specifically, there are two problems that need to be addressed for us to continue supporting the Mac OS X 10.6 platform, namely bug fixing and building of Mac OS X binaries. ![]() In other words: OpenTTD sometimes fails on Mac OS X 10.6.Īs the number of Mac OS X specific bugs is rising quickly (at September 22nd, 2009, one in four open bugs is Mac OS X related), the situation is getting out of control, and we are forced to reconsider the position of the Max OS X port. ![]() Now Apple has released Snow Leopard (Mac OS X 10.6) which, according to the bug reports we are getting, is not fully backward compatible with the previous releases. With every subsequent release we were forced to either deprecate support for older versions or write elaborate work-arounds to keep OpenTTD running on the already supported versions and the newer version. Since the beginning of OpenTTD the Mac OS X port has been the problem child of OpenTTD. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |