The Framework is improperly signed. #1042
Description
This bug report was migrated from our old Bugzilla tracker.
Reported in version: 2.0.0
Reported for operating system, platform: Mac OS X 10.6, All
Comments on the original bug report:
On 2013-08-23 17:39:15 +0000, dak180 wrote:
codesign -vvv /Volumes/SDL2/SDL2.framework/Versions/A
Yields:
/Volumes/SDL2/SDL2.framework/Versions/A: code or signature modified
On 2014-07-03 17:33:16 +0000, wrote:
This is causing crashes when spawning applications that use SDL2 under a debugger in Xcode 5. See http://stackoverflow.com/questions/22368202/xcode-5-crashes-when-running-an-app-with-sdl-2/24559954# 24559954.
On 2014-07-08 04:45:40 +0000, Sam Lantinga wrote:
I'm not super familiar with the Mac build tools. Is there something I should be doing during the release build process to fix this?
Here's the current build script:
(cd $PRODUCT-$VERSION-source/Xcode/SDL && xcodebuild -configuration Release -target "Standard DMG" >>$LOG && cp build/$PRODUCT.dmg $TOP/$PRODUCT-$VERSION.dmg) || exit 1
On 2014-07-08 05:03:10 +0000, Sam Lantinga wrote:
I dug into this a little bit, and there's a special code signing step for the DMG build process, and I'm guessing this is failing.
I'll investigate further.
Thanks!
On 2014-07-08 06:41:21 +0000, Sam Lantinga wrote:
Bugs in the signing script, fixed:
https://hg.libsdl.org/SDL/rev/d095e572e0d5Thanks for the info!
On 2014-07-08 07:05:40 +0000, Sam Lantinga wrote:
Ah, I found the second problem. In Xcode 5, the signing step is run before the binaries are stripped.
Investigating...
On 2014-07-08 07:30:12 +0000, Sam Lantinga wrote:
Okay, I worked around that by stripping the binaries before signing them. Then, when Xcode strips the binaries again, they don't change, and the signature is still valid.
https://hg.libsdl.org/SDL/rev/9e23a50a63f7