Bug in source trees? was: adding new group

Subject: Bug in source trees? was: adding new group

From: Markian Hlynka <email@hidden>

Date: Tue, 8 Aug 2006 16:19:11 -0600

Delivered-to: email@hidden

Hi again. So, I've been playing with some of the things James suggested, and I have somehow managed to generate a new error.

With my Add settings like this:

Copy items to group's folder if needed(checked)

Reference type: relative to codegenproject

Recursively create groups

Add to targets: codegeneration

I believe the new thing was checking the 'copy' box. Now, when I try to do this, I get:

Alert: Could not copy /Users/markian/Documents/School/PhD/Development/CodeGen/Games/Go9by9 to /Users/markian/Documents/School/PhD/Development/CodeGen/codegeneration/Go9by9.

This makes no sense. Notice the difference in the path. The first one is correct: that's where the files are that I want to add. The second path makes no sense: There is no such path.. the sources reside OUTSIDE of the project directory which, IIRC, is why I had a source tree in the first place.

The source tree is also correct, I've checked in preferences and it's valid:

~markian/Documents/School/PhD/Development/CodeGen

the codegeneration folder is inside of the above source tree. The xcode stuff is in that codegeneration directory. The sources are in CodeGen/Games, CodeGen/Interface, etc. Inexplicably, a directory has appeared INSIDE of codegeneration/, called Go9by9.

Finally, and extremely disturbing, I have discovered that a file I was previously editing was lying about where it was, and I was overwriting something else. Damn good thing for CVS! I don't feel I can trust xcode for anything at the moment, and I desperately need to get this fixed up. Suggestions? Confirmation of bug? Workarounds?

Can anyone shed any light on this? I'm pretty sure this started happening in Xcode 2.3

Finally, why the heck, if I click on "file copy.h" does it NOT open that file in Xcode? And how do I make it always open in a WINDOW?

Thanks again,

Markian

On Aug 3, 2006, at 18:32, James Bucanek wrote:

Markian Hlynka wrote on Thursday, August 3, 2006:

First I went to targets and duplicated a target. Didn't seem to be a
problem. Then I went and clicked on files that didn't belong and
unchecked them. Is there an easier way to do this? It seemed far to
involved. There must be a single screen where I can remove files from
a target...?

There are several ways.

- Select all of the files that you want to add or remove at once. Opening the Info window or palette will present an aggregate info window. Setting or clearing the target in that window adds or removes all files in the group from that target at once.

- Open up the build phase of the target. Each build phase lists the files used to make that phase of the target. Removing or adding a file to a target is equievelent to removing or adding that file to a build phase of the target. Select the files you don't want and press delete.

The group and everything in it immediately turns bright red. When I
get info on the group, the paths are all bright red. What's going on
here, please? I've never had a problem before, but this is probably
the first time I've done this in Xcode 2.3

I can't think of any reason why that might have happened. I've been told that paths with spaces can be a problem, although I was under the impression that most of those issues had been resolved. Do any of your folder or filename contain spaces?

James Bucanek
____________________________________________________________________
Author of Beginning Xcode ISBN: 047175479X
<http://www.beginningxcode.com/>

----

"I meant," said Ipslore bitterly, "what is there in this world that truly makes living worthwhile?"
Death thought about it.
"Cats," he said eventually. "Cats are nice."

-Terry Pratchett, Sourcery

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/email@hidden This email sent to email@hidden

References:

>Re: adding new group (From: James Bucanek <email@hidden>)