• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Xcode 2.0 dependent project bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode 2.0 dependent project bug?


  • Subject: Xcode 2.0 dependent project bug?
  • From: Greg Hurrell <email@hidden>
  • Date: Sat, 30 Apr 2005 03:12:23 +0200

Now that Xcode 2.0 is officially out I can ask this question... Has anyone run into the following dependency bug?

First the setup:

1. Create Project A

2. Create Project B

3. Add Project B to Project A as a dependency (so that Xcode will build B before building A)

Now the bug:

4. Open Project A (from the Finder or within Xcode; makes no difference)

5. Try to open Project B. You'll get a message like this: "Error: Could not find file /full/path/to/project.xcode. Perhaps it was moved or deleted?" (look on the disk and you'll see it's still there).

7. Close Project A, then try to open Project B: it works.

8. Leave Project B open, open Project A: it works.

In summary, you can open as many interdependent projects as you like but you must open the dependencies first. If you try to open the project that depend on the dependencies first then you won't be able to open the dependencies.

If you have a dependency chain A->B->C, then you must open C then B then A. You cannot open A then B then C.

I can reliably reproduce this in about 10 different projects I have, so I don't think there are any corrupt project files at play. This are simple linear dependencies, not the "circular project references" referred to in the Xcode 2.0 release notes:

Circular project references (where for example project A contains a reference to project B, and project B contains a reference to project A) will result in Xcode being unable to properly close any project in the cycle. This can lead to problematic behavior in Xcode. To avoid this behavior, be careful to avoid creating project reference cycles in projects, and to break existing cycles by removing references from one or more projects.
Xcode 2.0 is wonderful and I love it; much faster and more stable. It improves on previous versions in so many ways but this one issue is a *major* inconvenience.

Interested to hear if anyone else is seeing this. I've already filed a bug for it (rdar://4103756/).

Cheers,
Greg
_______________________________________________
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


  • Prev by Date: RE: Problems With Quicktime 7
  • Next by Date: Re: Problems with Quicktime 7
  • Previous by thread: re: Problems with gcc 3.3 in Xcode 1.5
  • Next by thread: ZeroLink and SDKs can't be used together?
  • Index(es):
    • Date
    • Thread