Patches item #1471883, was opened at 2006-04-17 20:19 Message generated for change (Comment added) made by ronaldoussoren You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1471883&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: Python 2.5 Status: Open Resolution: None Priority: 5 Submitted By: Ronald Oussoren (ronaldoussoren) Assigned to: Martin v. Löwis (loewis) Summary: --enable-universalsdk on Mac OS X Initial Comment: This patch adds an --enable-universalsdk flag to configure. When this is used on a MacOS X system with Xcode 2.1 or later this can be used to create universal (aka "fat") binaries for python and its extensions. This patches updates configure.in, which means autoconf should be used before checking in the patch. I've tested the patch on Linux as well, it seems to have no bad effects there. This patch is a cleaned up version of the code behind the --enable- universal-sdk flag in the python24-fat tree at http://svn.pythonmac.org/ python24/python24-fat. ---------------------------------------------------------------------- >Comment By: Ronald Oussoren (ronaldoussoren) Date: 2006-04-18 21:05 Message: Logged In: YES user_id=580910 osxconfig.h is there because this patch compiles all sources with 'cc -arch i386 -arch ppc' as the compiler. This means we can't use sys.byteorder to determine the right value for BYTORDER because that will be wrong for one of the architectures. The value of BYTORDER is used during the compilation of the expat sources, which don't include Python.h and that's probably because it is 3th-party software. There is no dependency between --enable-framework and --with-universal- sdk. I've tested this patch both with and without --enable-framework. Writing this I notice that I haven't checked if --enable-framework without -- with-universal-sdk still works. I'll check that and remove the empty statement. -current-version doesn't include the micro release because the current build also doesn't do that. It seems to be safe to change this, but I'd have to test to be sure. ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2006-04-17 23:52 Message: Logged In: YES user_id=21627 I don't understand the rationale for Modules/expat/osxconfig.h. I thought there was some magic to make Python.h's WORDS_BIGENDIAN always correct. If so, BYTEORDER wouldn't be needed at all anymore. In Makefile.pre.in, the -install-name option seems to imply -enable-framework. If this is indeed a hard dependency, configuring with universal-sdk, yet without framework should make configure abort. If it's not a hard dependency, the linker command line should be corrected for the case of --disable-framework. Minor issues: - avoid empty statements; reverse the if test "${enable_universalsdk}"; test - shouldn't the -current-version include the micro release? ---------------------------------------------------------------------- Comment By: Ronald Oussoren (ronaldoussoren) Date: 2006-04-17 20:24 Message: Logged In: YES user_id=580910 My patch refers to osxconfig.h, but that file isn't in the patch :-(. I've uploaded it seperately, it should be saved as Modules/expat/osconfig.h. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1471883&group_id=5470 _______________________________________________ Patches mailing list [email protected] http://mail.python.org/mailman/listinfo/patches
