Re: Xcode 4 Release Builds
Re: Xcode 4 Release Builds
- Subject: Re: Xcode 4 Release Builds
- From: Quincey Morris <email@hidden>
- Date: Thu, 21 Jul 2011 22:39:39 -0700
On Jul 21, 2011, at 21:05, Seth Willits wrote:
> What was nice with my Xcode 3 setup is I always had everything in the same ~/build/Release folder so it was always super simple to get the build products. In fact, my "Release" folder is in my Finder sidebar since I use it so often.
>
> So I guess the answer to my question is there really isn't anything this simple in Xcode 4.
I agree that Xcode 4 is less than perfect in this area, so I'm not saying this with the purpose of defending it, but ...
a. I don't understand why you're getting a folder hierarchy from the "Share" option. My guess is it's something to do with the installation/deployment build settings. (E.g. if it thinks you've asked for deployment into /Applications, it might be doing this to remind you that the shared app is not in the intended place.) But it's weird.
b. I don't understand your aversion to creating a scheme to build the Release configuration easily. Why do you feel the need to call this "abuse" (other than an understandable general desire to kick Xcode 4 with steel-tipped boots)? Schemes *are* the generalization of configurations (although obviously they don't do away with configurations), and switching to the correct configuration is required in Xcode 3 too, for the kind of semi-release scenario you're describing.
c. I could *swear* I saw an Xcode build settings setup (reading the Xcode 4 Guide when it was first released) that exactly mimicked the Xcode 3 build folder setup, for the explicit purpose of interoperating with the Xcode 3 workflow. It's a preference that says to honor the build settings for the output directories, instead of ignoring them. You didn't say whether or not you looked for this.
d. You can put a Derived Data folder in your sidebar, too. The only question is whether you can share a single Release folder for all the Release-configuration products of all your projects. I'm pretty sure the answer to that question is "Yes", if you set the preferences accordingly.
[My boot disk seems to have died, and I'm running on a restored backup on an external disk for now, so I don't really have access to Xcode 4 till I get things rebuilt. That's why there's a lot of "should be able to" and hand-waving in this response.]
> - Often wait for complete rebuild (it's losing intermediates?)
Are you saying you think this is a bug? Although I haven't seen it documented, the Archive function *always* rebuilds the product completely, presumably to ensure that you can't release something that uses out-of-date intermediate output. Although it's slower, it seems like a good new feature to me.
That's based, of course, on the assumption that Archive is for releases, which means it expects you're not going to be doing that a whole lot. I can't remember whether Build for Archive also rebuilds everything -- it may not.
Also, barking up the same tree as before, that's another reason why a scheme that builds to the Release configuration is advantageous. It certainly isn't going to rebuild everything each time (and you get to use Command-B).
P.S. I wonder whether there is in fact something in the build settings that would help you. If, in fact, there is a combination of installation/deployment settings that will actually "install" your application (even, say, in ~/Applications), it seems to me you're problem is mostly solved, because you won't need to extract anything from the Archive at all.
_______________________________________________
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