• 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: Xcode compatibility with third party compilers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode compatibility with third party compilers


  • Subject: Re: Xcode compatibility with third party compilers
  • From: Jonas Maebe <email@hidden>
  • Date: Sat, 5 Sep 2009 22:14:39 +0200


On 05 Sep 2009, at 21:09, Jonas Maebe wrote:

I fully agree there. Dead code stripping was indeed turned on by default in Xcode 3.2

Actually, it's not. A user had previously reported that - no_dead_strip_inits_and_terms solved the library-related linker problems for him under 10.6, but that must have been coincidence due to the fact that this option enables dead code stripping (and the interplay between that and reordering may have accidentally put code in a working order).


I also apologise for the related snide comments.


Jonas _______________________________________________ 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: 
 >Xcode compatibility with third party compilers (From: Jonas Maebe <email@hidden>)
 >Re: Xcode compatibility with third party compilers (From: Jonas Maebe <email@hidden>)

  • Prev by Date: Re: Xcode compatibility with third party compilers
  • Next by Date: Re: Static analyzer being lazy
  • Previous by thread: Re: Xcode compatibility with third party compilers
  • Next by thread: Gcc 3.3 support in XCode 3.2
  • Index(es):
    • Date
    • Thread