> On Aug 25, 2016, at 3:30 PM, Bill Cheeseman <wjcheese...@gmail.com> wrote:
>
> Apple's Cocoa framework header files have permissions 644, or u+w,go-w,a+r.
> All of the third-party framework header files I have ever examined have
> permissions 755, or u+w,go-w,a+rX, instead -- meaning that the headers are
> marked as executable. A number of online commentaries say that all framework
> header files should have permissions 644, as Apple's do, because headers are
> not executable, and that makes sense to me.
>
> But I can't figure out how to configure the Xcode build settings for my own
> framework to accomplish this.
I stumbled upon the solution, mostly by trial and error. Set the ALTERNATE_MODE
(Alternate Install Permissions) Deployment build setting to a-x, and set the
ALTERNATE_PERMISIONS_FILES (Alternate Permisions Files) Deployment build
setting to a list of your header files in this form:
"${BUILT_PRODUCTS_DIR}/PFAssistive.framework/Headers/PFUIElement.h".
Given the example of Apple's Cocoa framework header files, I suggest that all
developers of frameworks for macOS should do this.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
