d2ef2e17d1
It's been reported that the latest version of Tux Paint does not run on macOS 10.7 (Lion). This change fixes the issue. BACKGROUND A user has reported Tux Paint 0.9.23 does not run on macOS 10.7. She also identified that the issue is due to a system library required by Tux Paint, /System/Library/Frameworks/CoreGraphics.framework does not exist on macOS 10.7 Some investigation revealed that CoreGraphics.framework is a library required by libSDL, and it exists under an alternate path in macOS 10.7, underneath /System/Library/Frameworks/ApplicationServices.framework/Frameworks/. CoreGraphics.framework also exists underneath this path in newer version of macOS as a symlink to the real directory as well, so the issue can be fixed by simply relinking SDL to use the old (compatible) path instead of the new (default) path to CoreGraphics.framework. This change adds the code such that, during the `make install` step to create TuxPaint.app, any library referencing CoreGraphics.framework is re-linked to the compatible path rather than the path that only exists on the newer version of macOS. For more information, see: https://stackoverflow.com/questions/20206985/xcode-linking-against-applicationservices-framework-with-sdk-10-9-causes-10-7 |
||
|---|---|---|
| .. | ||
| macos-mkdmg.sh | ||
| macos.sh | ||
| README.txt | ||
| win32.bat | ||
Tux Paint Customization This folder allows for customization of Tux Paint. One example is adding resources such as fonts, stamps, starters... On Mac OS X, at the very end of the build, macos.sh script in this folder is run. On Windows, the win32.bat in this folder has to be run manually. At some point, a calling to the script could be integrated in the build process so as to be run automatically, just like it is on Mac OS X (see above). On Linux, it should be straightforward to replicate the process describe above on Mac OS X, and automatically call a linux.sh script, in this folder, from the build process.