• 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: Why should we not use GCC 4.0 for deployment on systems earlier than Mac OS X 10.3.9?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why should we not use GCC 4.0 for deployment on systems earlier than Mac OS X 10.3.9?


  • Subject: Re: Why should we not use GCC 4.0 for deployment on systems earlier than Mac OS X 10.3.9?
  • From: Simon Harms <email@hidden>
  • Date: Fri, 1 Jul 2005 12:26:10 +1000


There is a setting to cross develop using target SDK which allows you to compile to a target OS say MACOSX10.1.5
You can alter this setting by selecting Project from the main menu
Then choose Edit Project Settings
Then Cross DEvelop Using Target SDK is about half way down

Hope that helps

Simon Harms


From: Pavol Markovic <email@hidden>
Date: 30 June 2005 5:48:40 PM
To: XCode Users <email@hidden>
Subject: Re: Why should we not use GCC 4.0 for deployment on systems earlier than Mac OS X 10.3.9?


On Jun 28, 2005, at 2:40 AM, Nick Zitzmann wrote:



On Jun 27, 2005, at 5:40 PM, João Varela wrote:


I have been reading the documentation of GCC to see the caveats of this compiler and I really wanted to start using GCC 4.0 because it makes smaller code at faster compiling speeds. However, the docs state that we SHOULD NOT use GCC 4.0 if we want to deploy on systems earlier than Mac OS X 10.3.9. It is not said we CANNOT, only that we SHOULDN'T. My question is: why shouldn't we?


When linking binaries, GCC 4 does two things very differently from 3.3:

1. GCC 4 links C++ code to a shared libstdc++ library; GCC 3.3 uses a static library instead.
2. GCC 4 links all code to libmx; GCC 3.3 does not unless otherwise requested.

#1 breaks the app on versions of Mac OS X prior to 10.3.9, which don't have a dynamic C++ library. #2 breaks the app on versions of Mac OS X prior to 10.3.0, which don't have libmx.


Is it possible to make static libstdc++ library from gcc sources and link against this? Could this way work out? I've tried it but with no success so far. I'd like to use gcc4 optimizations and also support 10.2 systems.

Palo Markovic



 _______________________________________________
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: Why should we not use GCC 4.0 for deployment on systems earlier than Mac OS X 10.3.9?
      • From: Nick Zitzmann <email@hidden>
  • Prev by Date: Re: Xcode eating hard drive
  • Next by Date: Re: Xcode eating hard drive
  • Previous by thread: Re: Why should we not use GCC 4.0 for deployment on systems earlier than Mac OS X 10.3.9?
  • Next by thread: Re: Why should we not use GCC 4.0 for deployment on systems earlier than Mac OS X 10.3.9?
  • Index(es):
    • Date
    • Thread