• 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: Don't really understand why there are so many settings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Don't really understand why there are so many settings


  • Subject: Re: Don't really understand why there are so many settings
  • From: Greg Guerin <email@hidden>
  • Date: Sun, 11 Feb 2007 18:51:02 -0700

Theodore H. Smith wrote

>I do keep external backups but that's just in the event of total system loss.

So you have no earlier backup to help you recover from self-inflicted losses?


>Well... it used to work. I only need one root symbol actually. This is the
>one function that "Registers" all the other functions. I'm assuming that
>because one function refers to the other functions, the linker should keep
>them in. Well, it used to work that way.

Then go to the version that works, and compare the settings that work to
the ones that don't.

You could list and sort the settings to files, then do a 'diff' to automate
the process.

If you can't automate it, and you can't restore it from a previously
working backup, your only remaining choice is to switch Release settings to
match Debug settings one at a time, until Release starts working.  Or
change Debug to match Release until Debug stops working.

You could also do a binary search, changing half the settings at once, then
half again, until something starts working.  That takes some mad skilz at
keeping track of changes you make, or working on a disposable replica
instead of the original, or even making intermediate backups to a DMG, just
in case things get Munged Until No Good.

On the thin hope it could be something obvious, I suggest starting with the
settings that control dead-code stripping, symbol stripping, optimization,
etc.  If you can get symbols into the executable file, you can apply tools
like 'nm' and 'otool' to see if the file contains what you expect.  You can
also do this on the Debug output, just to get a sense of what symbols and
code-sizes to generally expect.

It all comes down to comparing what works with what doesn't, and isolating
it to the smallest change in settings that yields a difference.  If it
takes a few hours of mind-numbing drudgery, it's still an inexpensive
lesson about making backups before making major changes.

  -- GG


 _______________________________________________
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: Fast reading from files, using a pre-fetch approach?
  • Next by Date: Re: The bug where terminal and xcode ran "different"
  • Previous by thread: Re: Don't really understand why there are so many settings
  • Next by thread: Re: Don't really understand why there are so many settings
  • Index(es):
    • Date
    • Thread