Re: New 10.9.5 Gatekeeper rules (and a rant about them changing so often)
Re: New 10.9.5 Gatekeeper rules (and a rant about them changing so often)
- Subject: Re: New 10.9.5 Gatekeeper rules (and a rant about them changing so often)
- From: Dragan Milić <email@hidden>
- Date: Tue, 05 Aug 2014 21:59:42 +0200
On uto 05.08.2014., at 20.44, Seth Willits wrote:
> I'm far from an expert in code signing matters, but your issue sounds quite similar to one I had experienced in the past. Rather than using the resource rules file (I don't recall the details now, but I do remember finding it complicated to understand), I just added a single new Run Script phase to my top-level application's target that signed every framework within the bundle. In my case, I just did them explicitly, eg:
>
> LOCATION="${BUILT_PRODUCTS_DIR}"/"${FRAMEWORKS_FOLDER_PATH}"
> IDENTITY="Developer ID Application"
> codesign --verbose --force --sign "$IDENTITY" "$LOCATION/FMDB.framework/Versions/A"
> codesign --verbose --force --sign "$IDENTITY" "$LOCATION/Growl.framework/Versions/A"
> codesign --verbose --force --sign "$IDENTITY" "$LOCATION/HexFiend.framework/Versions/A"
> ...
>
>
> ... but if you write the script to recursively scan for .frameworks and .plugins and whatever else you have in your situation, I don't see why it would be more than a couple dozen lines or so to get that working, and not having to explicitly list all 65 built products from subprojects.
>
> Is there some reason that wouldn't work?
Yeah, I was thinking going that route, as my script to sign 3rd party frameworks already does similar thing. I just need to make it recursive and find everything that needs to be signed. However, I still hoped there’s more elegant solution and to really use Xcode for what it’s supposed to do and not write scripts myself. I found --resource-rules to be that elegant solution (and I didn’t really have any problems understanding it), but I guess I’m now left without that elegancy.
-- Dragan
_______________________________________________
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