| Summary: | The Framework is improperly signed. | ||
|---|---|---|---|
| Product: | SDL | Reporter: | dak180 <dak180> |
| Component: | build | Assignee: | Sam Lantinga <slouken> |
| Status: | RESOLVED FIXED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | major | ||
| Priority: | P2 | CC: | binarycrusader, h, jasoncrowder, sdlbug |
| Version: | 2.0.0 | ||
| Hardware: | All | ||
| OS: | Mac OS X 10.6 | ||
|
Description
dak180
2013-08-23 17:39:15 UTC
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. 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 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! Bugs in the signing script, fixed: https://hg.libsdl.org/SDL/rev/d095e572e0d5 Thanks for the info! Ah, I found the second problem. In Xcode 5, the signing step is run before the binaries are stripped. Investigating... 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 |