This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients Ray.Donnelly, doko, ned.deily, ronaldoussoren
Date 2012-10-22.07:05:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350889525.65.0.300968273109.issue16291@psf.upfronthosting.co.za>
In-reply-to
Content
The patch itself looks fine, but I wonder how useful it will be.

A small question about the patch, why this case in the cross_arch function:

+	  x86_64*darwin*)
+	    echo i386

That doesn't look correct.


Back to the more important issue of the usefulness of this patch:

* Why is cross-compiling to OSX useful at all? You still have to test
  if the output of the compilation works, and for that you need
  an OSX system.

* The patch will only help with cross-compiling C code, it won't compile
  resource files (like the NIB file in Python Launcher)

  This is not a problem right now because that project currently contains
  older NIB files that can be used for editting and running, but would
  make it harder to move to the more modern XIB files that were introduced
  with Xcode 4.

* This will make support harder, I already get support questions where
  the answer depends on the way Python was build and that will likely
  get worse with cross-compiling.

* Where would users get the SDK? I'm not a lawyer (or even familiar with
  US law), but the Xcode license seems to indicate that it can only
  be used on Apple systems.
History
Date User Action Args
2012-10-22 07:05:25ronaldoussorensetrecipients: + ronaldoussoren, doko, ned.deily, Ray.Donnelly
2012-10-22 07:05:25ronaldoussorensetmessageid: <1350889525.65.0.300968273109.issue16291@psf.upfronthosting.co.za>
2012-10-22 07:05:25ronaldoussorenlinkissue16291 messages
2012-10-22 07:05:25ronaldoussorencreate