• 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: Using newer version of gcc for shared libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using newer version of gcc for shared libraries


  • Subject: Re: Using newer version of gcc for shared libraries
  • From: Eric Albert <email@hidden>
  • Date: Sat, 26 Nov 2005 23:37:23 -0800

On Nov 25, 2005, at 12:06 PM, Dave Rehring wrote:

I've done some searching in the Xcode release notes/documentation and this
mailing list, but I can't find any mention of if it's OK to use a dylib
built with xcode v2.2/gcc 4.0.1 in an app that's currently being built using
xcode v2.1/gcc 4.0.0? The library in question is the icu v3.2 library,
which exposes some C++ bugs in the gcc 4.0.0 compiler.

This should be fine. Due to C++ ABI changes you can't use pre-4.0 C+ + libraries with 4.0 or later versions of gcc, but the ABI should be stable as of 4.0.


Hope this helps,
Eric

_______________________________________________
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: 
 >Using newer version of gcc for shared libraries (From: Dave Rehring <email@hidden>)

  • Prev by Date: Re: Problem finding c++ headers...
  • Next by Date: Use native precompilation checkbox oddity
  • Previous by thread: Using newer version of gcc for shared libraries
  • Next by thread: Prevent warnings on forward struct declaration
  • Index(es):
    • Date
    • Thread