Re: Xcode 4 Copy Files Build Phase Infinite Loop
Re: Xcode 4 Copy Files Build Phase Infinite Loop
- Subject: Re: Xcode 4 Copy Files Build Phase Infinite Loop
- From: Thomas Wetmore <email@hidden>
- Date: Tue, 22 Mar 2011 07:04:23 -0400
Jerry,
Thanks. No, this doesn't crash Xcode. I can stop it. Note, however that there is little indication that it is happening. Only in the build history log under the build history tab in the project navigator can you see the problem, with the spinning indicator. Interestingly, when I stop the build by pushing the stop button and look at the result in the project navigator, I always get the big green success check mark! I have found other things that I do make Xcode 4 unresponsive and have to force quit it. This is not one of them. I have none of these problems with Xcode 3.
I have experimented further with this issue, but have not found a solution. I thought maybe it had to do with the the location of the .a file in the hard-wired location in ~/Library/Developer/Xcode/DerivedData/... location where it is created. I also need a copy files phase to move the library's header files to a standard location. I have found that that copy file phase sometimes works, but it to sometimes leads to the "infinite loop." These extra steps are identical to phases I have in the Xcode 3 equivalent projects.
All in all I have found Xcode 4 very unstable, with many very simple operations causing it to go either "infinite" or unresponsive. It is not a finished product.
I have found the Workspace feature unusable so far. Following all instructions to the letter I cannot create a Workspace with more than one project in it (that actually works). And my projects are very small and totally vanilla, a couple small static libraries, a couple foundation-based command line utilities, and a few simple Cocoa applications. The only out of the ordinary thing I do is use yacc files to generate parsers, and I use the nice feature in Xcode that allows the yacc file to include Objective-C code instead of C code, and another nice feature that allows multiple yacc files to be used in the same application. These features are implemented well in Xcode 3 and fortunately made it through to Xcode 4 (though see my complaint about warnings in the next paragraph). I am in fact extremely pleased with how well Apple supports yacc users. That was unexpected to be honest.
Have you found a way to take control of the build location? Took me a little while to discover where all my object files and .a's were going. Using yacc/bison causes some objective-C files to be created from yacc files. When I get warnings from the generated files, navigating to the warnings pop up the original yacc files (as it should), but the yacc files are not tagged with the warning locations, and there is no easy way to go look at the generated .m files. With Xcode 3 I would put a new group in the project navigator for these generated files. I'll do the same for Xcode 4 I hope. So Xcode 4 is smart enough to know what files to flag to the user to looking for the warnigns, but isn't smart enough to show where in the file to look.
Tom Wetmore
On Mar 22, 2011, at 4:46 AM, Jerry Gagelman wrote:
> I've seen this before too, particularly when the target is a command line utility and I add build phase to copy it from the derived data location. I simply thought the problem was some setting that I had wrong.
>
> One more question for you: the build doesn't crash Xcode, does it? Namely, does selecting Product > Stop terminates the build without further issue?
>
> Incidentally, in previous developer previews of Xcode 4, this feature worked for me. I'll file a radar.
>
> -- Jerry
>
> On Mon, Mar 21, 2011 at 19:11, Thomas Wetmore <email@hidden> wrote:
> I am moving my projects to Xcode 4 and am having difficulties. Here is one.
>
> I have an Xcode 3 project that creates a static library used by many other projects. In the Xcode 3 target I added a copy files build phase that moves the library to ~/lib. When I add the identical copy files build phase to the Xcode 4 target, the build goes into la-la land and never returns. I make the same selections as in Xcode 3, choosing Absolute Path and adding ~/lib to the Subpath (it makes no difference if I use the full absolute path instead). If I remove the phase it works, add it back, la-la land, etc.
>
> Has anyone else seen this behavior? I was originally trying to create an Xcode 4 workspace with the library as one of the projects so I wouldn't have to copy the library anywhere, but that's a whole other story of frustration.
>
> Tom Wetmore _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
>
>
>
> _______________________________________________
> 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
_______________________________________________
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