• 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
Re: deployment vs. development style weirdness
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: deployment vs. development style weirdness


  • Subject: Re: deployment vs. development style weirdness
  • From: email@hidden
  • Date: Thu, 16 Sep 2004 16:26:51 +0000
  • Importance: Normal
  • Sensitivity: Normal

>
> On Sep 16, 2004, at 9:37 AM, email@hidden wrote:
>
> > Why is this idiocy happening?  Is this a bug?
>
> When ZeroLink is enabled, link errors aren't detected until the task is
> running. If ZeroLink wasn't enabled, then the error would have appeared
> during the build process when the code was being linked. This is not a
> bug, because this is the way ZeroLink works - the code is linked on the
> fly instead of having it done as part of the build process.
>
> Nick Zitzmann

I agree with that being a logical behavior.  What I didn't understand was why

(1) a foundation tool is a valid option when you start a new project and it is set up to link against foundation

(2) is an UNexisting option when you create a new target?

In my Xcode 1.5 installation, when I select a Project->New Target the closest entry to a Foundation Tool was Cocoa Shell Tool, which I selected when I was setting up my tool target.

I guess I am trying to understand the logic of things so I don't have to wander aimlessly around the menus or look up manuals every time I want to do something simple.  So unless I have things messed up completely, I can't understand the logic for the above behavior.  Can anyone please explain?

Thanks,

-- ivan

>
> Now that I think about it, Xcode's developers probaly intended for it to be exactly this way.  When I was adding my second target (the command line tol) to the project, Xcode didn't  even offer me a possibility of choosing a Foundation Tool for the target type (unlike what Xcode does when you start a new clean project, then you do have a choice of Foundation command-line tool).
>
> Why is this idiocy happening?  Is this a bug?  Why are the types ot targets offered when you add a target different from the types of projects offered when you create a project (that is, single targets)?  Is this logical or is there something I am missing?
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: deployment vs. development style weirdness
      • From: Nick Zitzmann <email@hidden>
  • Prev by Date: Re: Zerolink as a default option
  • Next by Date: [Q] Bindings, FilteringController and KVC compliance
  • Previous by thread: Re: deployment vs. development style weirdness
  • Next by thread: Re: deployment vs. development style weirdness
  • Index(es):
    • Date
    • Thread