• 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 3.2 libtool, ld64
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 3.2 libtool, ld64


  • Subject: Re: Xcode 3.2 libtool, ld64
  • From: Peter O'Gorman <email@hidden>
  • Date: Fri, 04 Sep 2009 12:41:03 -0500

Jonas Maebe wrote:
>
> b) what is the best backwards and forward compatible way (in terms of
> "the command line can remain identical") to link dylibs? gcc nowadays
> calls "collect2". Is there a reason why we should not call ld directly?
> I called libtool because I thought that it might (one day) do some extra
> things behind the scenes, and didn't want us to risk suddenly breaking
> at that point. Obviously, that did not work out so well.
>

Hi,

I know that it's ugly, but, in my opinion, the most compatible way to do
this is for your compiler to call Apple's compiler for the link step,
not ld or libtool (I believe this is what icc does).

Peter
--
Peter O'Gorman
http://pogma.com
 _______________________________________________
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

  • Follow-Ups:
    • Re: Xcode 3.2 libtool, ld64
      • From: Jonas Maebe <email@hidden>
References: 
 >Xcode 3.2 libtool, ld64 (From: Jonas Maebe <email@hidden>)

  • Prev by Date: Re: documentation window scrolls its contents spontaneously
  • Next by Date: Re: documentation window scrolls its contents spontaneously
  • Previous by thread: Xcode 3.2 libtool, ld64
  • Next by thread: Re: Xcode 3.2 libtool, ld64
  • Index(es):
    • Date
    • Thread