Messing with the executable ...
Messing with the executable ...
- Subject: Messing with the executable ...
- From: Alexander von Below <email@hidden>
- Date: Mon, 05 Dec 2011 17:22:04 +0100
Hello List,
I need to mess with my iOS Executable after it has been built, but before the Code Signing Phase. This is due to an apparent bug in the Application Loader, which will not accept an armv7 only binary even if the minimum deployment target is set to iOS 4.3 (We have filed a DTS Request, 172678777)
Therefore, I want to create a fat binary by add a dummy armv6 part.
So I have introduced a Custom Script Phase after Linking, and looking at my log it appears that it is executed right when it should be. However, at the end of the process Xcode gives me a warning:
warning: Application failed codesign verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate. (-19011)
codesign_wrapper-0.7.10: using Apple CA for profile evaluation
AssertMacros: 1 == fread(&lc, sizeof(lc), 1, binary), file: codesign.c, line: 205
No LC_CODE_SIGNATURE segment found
This can not be remedied later (say, with the "Share" option from the Organizer).
Now, does anyone have an a guide for a "best practice of messing with your executable"? And where should I mess with it?
In "$BUILT_PRODUCTS_DIR/$EXECUTABLE_PATH", in "$CODESIGNING_FOLDER_PATH/$EXECUTABLE_NAME", or somewhere else?
Alex
P.S.: Yes, we must use Application Loader. Our paranoid IS Department will not allow the build machine to have a connection to the outside world. And they won't allow us to build the product on another machine, either.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden