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 set the Deployment build setting ALTERNATE_MODE (Alternate Install Permissions) to u+w,go-w,a+r, instead of the default u+w,go-w,a+rX. But I haven't found a workable way to set the ALTERNATE_PERMISSIONS_FILES (Alternate Permissions Files) setting. This setting is supposed to contain the paths to the framework header files, but every way I have tried to construct the paths either accomplishes nothing or causes the build to fail because the header files aren't found. Can anybody explain how to set ALTERNATE_PERMISSIONS_FILES to accomplish my goal? (I assume I can fall back on a run script build phase calling CHMOD -- right? But I would like to know how to use the ALTERNATE_PERMISSIONS_FILES build setting, which seems to be designed specifically to do this sort of thing.) _______________________________________________ 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
