Xc6 won’t archive standalone OS X frameworks?
Xc6 won’t archive standalone OS X frameworks?
- Subject: Xc6 won’t archive standalone OS X frameworks?
- From: Fritz Anderson <email@hidden>
- Date: Fri, 21 Nov 2014 15:56:41 -0600
Due diligence before filing the bug…
Has anyone managed to produce a standalone .framework bundle for OS X lately? Xcode 6 won’t give me an archive.
OS X 10.10.1
Xcode 6.1.1 seed and 6.2 first beta
Latest SDK (10.10), latest-OS target, development-system architecture.
I’d like to build an OS X .framework as a standalone product — a shareable library and resource package like Mom used to make in the ’00s.
My first attempt was:
- Start with a Mac application as a scaffold for developing the code and assets.
- When that's working, add a framework target and transfer all the assets from the application target, (Nice: Under Xc6, the path-and-copy dance for the usual case of embedding a framework in an application is done automatically. But “labor-saving” isn’t the same as “labor saved,” as this case may illustrate.)
- Satisfy myself that the library works the same now that it’s in a separate binary.
- Select the framework’s build scheme and Product > Archive. The target’s build goes through, no problem.
- The scheme says the Archive organizer should open now, so I can save a distributable product. It doesn’t. The organizer doesn’t even show the framework target. When I tracked down the ~/Library… /Archives folder, there was an archive for every attempt, but they were all empty.
- Being a dependency of the application target, the completed framework bundle does appear among the app’s build products, but the access exceptions that come of using it standalone suggest that it’s not the Real Thing. (Only “suggest,” because — sorry — the tools are in flux, and I’m monthis into a run of conspicuous bugs.)
Starting from a framework-only project does no better.The Xc6 release notes mention nothing like this. (The Framework Programming Guide goes into detail on prebinding, by the way.) All-Swift or all-C, no difference. I’ve tried nudging the settings for installation locations, when-installing conditions, Embedded content contains Swift, etc.. Maybe I haven’t struck on the right combination because, once again: It just can’t be that this isn’t possible.
— F
_______________________________________________
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