Re: Archiving Frameworks?
Re: Archiving Frameworks?
- Subject: Re: Archiving Frameworks?
- From: Seth Willits <email@hidden>
- Date: Mon, 11 Aug 2014 11:04:34 -0700
On Aug 7, 2014, at 5:55 PM, Seth Willits <email@hidden> wrote:
> I've never thought about it before: Are you supposed to be able to archive a framework? It successfully builds, but all it does is spit out an empty .xcarchive folder.
Learned:
1) Install Path cannot be @rpath, and cannot be empty.
2) Skip Install must be NO.
The problem with #2 is that if installing is left on, then the archive of an application that has an inter-project dependency on this framework will contain the framework as well, which is a real nuisance.
The archive's Products directory contains both:
/Users/seth/Applications/My.app
/Library/Frameworks/My.framework
And because of that, the Organizer doesn't recognize the archive as "an application" and instead sees it as a generic archive with no version, etc. And, because of *that*, you can't use the organizer to do Validate/Submit/Export options you would with a normal application archive.
Setting Skip Install on the framework's target to Yes makes the application's archive nice and clean exactly as I want, but then doesn't allow archiving the separately on its own. (Not that I particularly need it, but it's a conflict.)
--
Seth Willits
_______________________________________________
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