Xcode 9 vs SIP: how to build & copy to /Library/Frameworks on 10.13?

I'm building a Framework that is meant to be accessible by multiple apps, and therefore installed in /Library/Frameworks


Beginning with High Sierra, this location appears to be protected by SIP. It is impossible to make the directory writeable by the current user or group (AFAIK), which happend to be the method I used until 10.12.x to allow Xcode to build and copy my framework directly at its install location.


What would be the strategy to get this done in High Sierra? I hope I'm overlooking something because the thought of having to drag files in the Finder and authenticate every time I want to copy something to /Library/Frameworks makes me cringe.


Thanks!

Gabe

FxFactory

Up vote post of FxFactory Down vote post of FxFactory
641 views
Posted by
FxFactory
Reply
Add a Comment

Replies

It was never a good idea to change the permissions of a directory like that. I suppose you could always write some script to copy those files without authentication. Or you could install into ~/Library/Frameworks instead.

Posted by
john daniel
Up vote reply of john daniel Down vote reply of john daniel
Add a Comment

>> Or you could install into ~/Library/Frameworks instead.


Yes, you don't need the system /Library/Frameworks for multiple apps, only for multiple login users.


However, if the apps themselves were previously installed in system /Applications, then it may be necessary to move them for consistency.

Posted by
QuinceyMorris
Up vote reply of QuinceyMorris Down vote reply of QuinceyMorris
Add a Comment

Thank you all, indeed building and deploying to the Home folder seems to be the only option at this time (I am not fond of disabling SIP). The fact that the Home folder is automatically added to the loader search paths is great, but this is a step back for those in my fringe situation: multi-user and multi-app testing.


So in the current Xcode 9 + High Sierra one has to be prepared to either copy the framework(s) to be tested in the Local Domain (/Library/...) before switching to other accounts, or perhaps automate the process via an AppleScript that requires admin authentication. This might be one case where the Touch ID sensor saves our sanity :-)


Happy coding!

Gabe

Posted by
FxFactory
Up vote reply of FxFactory Down vote reply of FxFactory
Add a Comment