• 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: Porting windows app to OS X and it's extremely huge as a result
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Porting windows app to OS X and it's extremely huge as a result


  • Subject: Re: Porting windows app to OS X and it's extremely huge as a result
  • From: Platon Fomichev <email@hidden>
  • Date: Sun, 25 May 2008 11:35:38 +0400

Thanks Ken

This is an excellent and thorough answer. I have just one small point of interest left - we still have 4.0.1 on Leopard as far as I now know, but another build. What does 4.0.1 then mean - a base GCC version used for the compiler? Also do you per-chance know whether XCode 3 contains any specific document about compiler changes in Leopard - there should be definitely some changes to support garbage collection f.ex. (I've checked internet available docs to no avail and I don't have Leopard installed anywhere yet).

Best regards,
            Stauff__

On May 25, 2008, at 07:33 AM, Ken Thomases wrote:

On May 24, 2008, at 5:04 PM, Platon Fomichev wrote:

Thanks for your help. Indeed I am using latest Tiger XCode with GCC 4.0.1 (gcc version 4.0.1 (Apple Computer, Inc. build 5370)) on OS X 10.4.11. I will try rebuilding stuff on Leopard and hopefully it will work backwards on Tiger (I see no reasons why it should not).

You will need to specify "-isysroot /Developer/SDKs/MacOSX10.4u.sdk -mmacosx-version-min=10.4" to all invocations of gcc/g++. If you invoke ld directly (rather than using gcc/g++ as a front-end to the linker), you'll need to supply "-syslibroot /Developer/SDKs/ MacOSX10.4u.sdk -macosx_version_min 10.4".


Setting the SDK makes sure your code doesn't make use of Leopard- only API. Setting the minimum deployment version makes sure the compiler and linker only use features of the Mach-O object file format which are compatible with the specified deployment target.

Apple refers to building on one OS version while targeting deployment on a different OS version as "cross-development": http:// developer.apple.com/documentation/DeveloperTools/Conceptual/ cross_development/

Also, see these links for some related details:

http://developer.apple.com/releasenotes/Darwin/SymbolVariantsRelNotes/
http://developer.apple.com/releasenotes/Darwin/RN-Unix03Conformance/

Cheers,
Ken

_______________________________________________ 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: Porting windows app to OS X and it's extremely huge as a result
      • From: Jonas Maebe <email@hidden>
References: 
 >Re: Porting windows app to OS X and it's extremely huge as a result (From: Platon Fomichev <email@hidden>)
 >Re: Porting windows app to OS X and it's extremely huge as a result (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: Porting windows app to OS X and it's extremely huge as a result
  • Next by Date: Re: Porting windows app to OS X and it's extremely huge as a result
  • Previous by thread: Re: Porting windows app to OS X and it's extremely huge as a result
  • Next by thread: Re: Porting windows app to OS X and it's extremely huge as a result
  • Index(es):
    • Date
    • Thread