Revision 32194 Author mww@macports.org Date 2007-12-19 06:44:11 -0800 (Wed, 19 Dec 2007)
Log Message make the universal flags take the archs from a single source (thanks to ryandesign for the idea), enable 64 bit universal builds
This change makes all +universal ports with an UI based on Carbon break, since it (Carbon) doesn't support 64-bit... (and especially not x86_64) http://developer.apple.com/documentation/Carbon/Conceptual/ Carbon64BitGuide/ "Most APIs in Mac OS X v10.5 are available to both 32-bit and 64-bit applications, but some APIs commonly used by Carbon applications are not. In particular, the APIs used to implement a Carbon user interface are generally available only to 32-bit applications. If you want to create a 64-bit application for Mac OS X, you need to use Cocoa to implement its user interface." Never mind that it also makes each one twice as big (4 times the original)
+# +# internal functions to determine the "-arch xy" flags for the compiler +# -> these should preferably get a more global scope, perhaps be user-configurable? +set universal_archs {ppc ppc64 i386 x86_64} +
This should probably be reverted back to "set universal_archs {ppc i386}" ? --anders
On 8 Jan 2008, at 09:34, Anders F Björklund wrote:
Revision 32194 Author mww@macports.org Date 2007-12-19 06:44:11 -0800 (Wed, 19 Dec 2007)
Log Message make the universal flags take the archs from a single source (thanks to ryandesign for the idea), enable 64 bit universal builds
This change makes all +universal ports with an UI based on Carbon break, since it (Carbon) doesn't support 64-bit... (and especially not x86_64)
http://developer.apple.com/documentation/Carbon/Conceptual/Carbon64BitGuide/
"Most APIs in Mac OS X v10.5 are available to both 32-bit and 64-bit applications, but some APIs commonly used by Carbon applications are not. In particular, the APIs used to implement a Carbon user interface are generally available only to 32-bit applications. If you want to create a 64-bit application for Mac OS X, you need to use Cocoa to implement its user interface."
Never mind that it also makes each one twice as big (4 times the original)
+# +# internal functions to determine the "-arch xy" flags for the compiler +# -> these should preferably get a more global scope, perhaps be user-configurable? +set universal_archs {ppc ppc64 i386 x86_64} +
This should probably be reverted back to "set universal_archs {ppc i386}" ?
This should definitely be made user-configurable. Most people will actually be interested in building 32 and 64 bit for their machine, that is either ppc+ppc64 or i386+x86_64. Regards, -Markus -- Dipl. Inf. (FH) Markus W. Weissmann http://www.mweissmann.de/
On Jan 8, 2008, at 00:54, Markus Weissmann wrote:
This should definitely be made user-configurable. Most people will actually be interested in building 32 and 64 bit for their machine, that is either ppc+ppc64 or i386+x86_64.
Yes, please! 64-bit Intel is the only thing I need 'universal' for =)
participants (3)
-
Anders F Björklund
-
Landon Fuller
-
Markus Weissmann