• 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 bug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode bug


  • Subject: Xcode bug
  • From: Ambroise Confetti <email@hidden>
  • Date: Sun, 26 Oct 2003 23:33:35 +0100

Hi all,

I just encountered a very unpleasant bug in Xcode which made my project totally unreadable (Xcode would crash trying to open it again).

Here's how to do that, so that you DON'T do that.

By reading the Xcode Release Notes, I thought that the ability to create dependencies to targets located in other projects was something great (my application has a lot of plug-ins and preference panes which I can now put in independent projects).

However... I just don't understand HOW they didn't catch that bug.

Here's the receipt (part of it may be enough but I really don't have the time to investigate -- however I had it twice so it IS easily reproducible):
- add an Xcode project "B" to an Xcode project "A"
- drag and drop B's target to some places in A where you want it to appear (in my case the Frameworks group, a Copy Files build phase and the "Dependencies" list that you access by inspecting A's target -- in the latter case, no new item appears in the list, however you just ignited the bug)
- change your mind and decide you want to remove it: select the newly created item and hit "Delete" (note it doesn't work)
- now, play a bit with targets, frameworks, try to drag and drop related things, build your project... Work. The exception should follow shortly.

Now, HOW to use external targets without causing the bug:
- add your other project normally as above
- NEVER make any drag and drop with the external target
- to add the dependency, click the "+" button under the dependencies list
- to add the target's product to any other place in your project, add the real product file instead

As I already said, I really don't have enough time to fill in a bug report (oh, by the way, I think the "Send a bug report to Apple" thing is totally Microsoft-like -- even as a freeware developer, I would be ashamed to have my users spend time to fix MY bugs, and Panther is not freeware, it's 149. By the way, was the French translation made by a machine? it's the worst I've ever seen for an operating system... There are things I need to translate back to English in order to understand the meaning. Luckily enough, Panther is great anyway).

However I didn't want that bug to happen to anybody here. As people from Apple will probably read this, consider this is a bug report (moreover, this is a bug that is likely to bother A LOT of users, so other bug reports should follow shortly).


Ambroise

http://www.cellulo.info/
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Xcode bug
      • From: mmalcolm crawford <email@hidden>
    • Re: Xcode bug
      • From: Clark Cox <email@hidden>
    • Re: Xcode bug
      • From: "Alastair J.Houghton" <email@hidden>
  • Prev by Date: Re: Error Code -2857
  • Next by Date: Re: Xcode bug
  • Previous by thread: metal/non-metal problem with nested splitviews
  • Next by thread: Re: Xcode bug
  • Index(es):
    • Date
    • Thread