• 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: Zerolink Yet Again...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Zerolink Yet Again...


  • Subject: Re: Zerolink Yet Again...
  • From: Phil Hystad <email@hidden>
  • Date: Thu, 25 Oct 2007 10:05:22 -0700

Shawn (and others),

Thanks for the comments and answers. I actually didn't think of zero- linking as disabling all linking functions. I sort of thought of it as disabling the link of external references since linking does take place (to a degree). Therefore, that is why I was surprised at the errors I saw.

However, now I must start thinking in terms of two linkers. The tiny linker used to bind executables for debug and the kind of linker used to create a stand-alone image. I think I will stick with the full linker for awhile.

phil

On Oct 25, 2007, at 9:42 AM, Shawn Erickson wrote:

On 10/25/07, Phil Hystad <email@hidden> wrote:
OK, I think every question I have asked on this forum so far has been
about zero link and yet again I have a question.

I was stumped by a zero link error so I turned zero link off and got
a half-dozen other errors on my project -- more then I expected.
Yes, I do admit this is the first time I turned off zero link on this
particular set of code but still.  All the errors were justified but
I was surprised that I needed to disable zero link to see them.
Errors like multiple defined variables and functions (I as gluing two
different systems together) were the bulk of the problems.

So, is it true that if you are using debug and zero link enabled that
such valuable information on your project build is ignored?

Zero link means that no linking is done at compile time, deferring it to runtime. The type of errors you are hitting will only be known when linking takes place... so if no linking takes place at compile time Xcode cannot warn you about those errors.

The intent of Zero Link is to avoid the time spent linking to speed up
the debug/fix cycle of development (minor fixes followed by trips into
the debugger to verify, etc). You shouldn't have it enabled when you
are doing large changes / bulk development.

Of course in general Zero Link has been more trouble then it was worth
for most developers, so most folks don't use it... in fact it is going
away IIRC.

-Shawn

_______________________________________________ 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
References: 
 >Zerolink Yet Again... (From: Phil Hystad <email@hidden>)
 >Re: Zerolink Yet Again... (From: "Shawn Erickson" <email@hidden>)

  • Prev by Date: Re: Zerolink Yet Again...
  • Next by Date: Re: Xcode not linking static library
  • Previous by thread: Re: Zerolink Yet Again...
  • Next by thread: Re: Zerolink Yet Again...
  • Index(es):
    • Date
    • Thread