[issue23670] Modifications to support iOS as a cross-compilation target

Change by Josh Rosenberg : -- title: Restore -> Modifications to support iOS as a cross-compilation target ___ Python tracker ___ __

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: For those interested, I've started tracking these patches on Github: https://github.com/freakboy3742/cpython The 3.4, 3.5 and 3.6 branches are tested and compile as of the time of this comment; the master branch has also been updated, in preparation for

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Mariatta Wijaya : -- nosy: +Mariatta ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue23670] Modifications to support iOS as a cross-compilation target

Todd Rovito added the comment: Russell, this is excellent work I am truly amazed that within a couple of hours I had Python built and running for the iOS simulator this is a feat I didn't think was possible. Perspective on me I am very familiar with Linux, C, and Python but know very lit

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue23670] Modifications to support iOS as a cross-compilation target

Luke Taylor added the comment: Ok, great! On Fri, Jun 3, 2016 at 7:34 AM Luke Taylor wrote: > Ah, cool! > On Fri, Jun 3, 2016 at 2:58 AM Russell Keith-Magee > wrote: > >> >> Russell Keith-Magee added the comment: >> >> Yes - I'm aware of Pythonista; the author of that app contracted me to >>

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Yes - I'm aware of Pythonista; the author of that app contracted me to develop the 3.5 patch that is attached to this ticket :-) -- ___ Python tracker ___

[issue23670] Modifications to support iOS as a cross-compilation target

Luke Taylor added the comment: Are you aware of Pythonista? I have no affiliation, but I'm a fan of the app and the community surrounding it. See http://omz-software.com/pythonista/ for details. I'm sure communication with the developer of the app could yield some useful insights. --

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Alex - The usual cause for that problem isn't regrtest (at least, not directly). The cause is one of the tests in the suite spawning a subprocess. Due to the way the test harness works, when the test suite forks/spawns a subprocess (e.g., to run a networ

[issue23670] Modifications to support iOS as a cross-compilation target

Alex Willmer added the comment: I've done my best to rebase Freakboy's patch onto 3.6-dev. The attached applies cleanly, but the testsuite goes into an infinite loop. It's a start at least. At a guess the problem is in Lib/test/libregrtest/ or Lib/test/regrtest.py where the patch changes sys.e

[issue23670] Modifications to support iOS as a cross-compilation target

Nick Coghlan added the comment: Mac OS X 10.5 was the last version to support PowerPC architectures, and according to https://en.wikipedia.org/wiki/Mac_OS_X_Leopard#Release_history, the final version of that was 10.5.8, released in August 2009. While we don't have a section in https://www.pyth

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Another update - the issue with libffi has been resolved, so there is now only need for a single copy of libffi_ios sources. This directory could potentially be merged with the libffi_osx sources, except that libffi no longer supports PowerPC as a compil

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Cory Benfield : -- nosy: +Lukasa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Marco Paolini : -- nosy: +mpaolini ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Another update - this time, there are only 4 failing tests on device, all related to ctypes issues. The sample Xcode project and iOS-test harness have been modified, simplifying the project layout, and using Apple-preferred directories for resources when

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Another patch update - the code now passes the full Python test suite on the iOS simulator. There are still a couple of failures on device; as before, these appear to be due to ctypes problems and a permissions issue with os.mkdir. -- Added file

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: This new patch (20150504.diff) adds support for running the Python test suite The new patch is standalone, and contains everything in the previous patch. An XCode project (Tools/iOS-test) has been added to the source tree; this project contains bootstrap

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Here's an updated patch that integrates some of the feedback that has been received so far. Notable changes: * The code now works for ARMv7. Unfortunately, the price for this is a new libffi_ios_aarch source directory, containing generated source tree

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Hi Matthias: * The libffi situation on iOS is much the same as it is on OS/X - it needs to be pre-generated. This can't be driven by the existing build system - libffi's Makefile requires a separate pre-generation step. There's certainly potential for r

[issue23670] Modifications to support iOS as a cross-compilation target

Matthias Klose added the comment: not reviewing everything, but - libffi_ios* will be bitrot. I understand that you'll need an unreleased version, however I would much prefer that any additional patches are added in the repo, and maybe then patching libffi from the iOS build system

[issue23670] Modifications to support iOS as a cross-compilation target

Ned Deily added the comment: Russell, we talked a bit about this topic at the Python Language Summit today (after watching your excellent video). I think there was general agreement there that having iOS support would be "a good thing" along with the recognition that the requirements for supp

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Ned Deily : -- assignee: -> ned.deily stage: -> patch review versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___

[issue23670] Modifications to support iOS as a cross-compilation target

R. David Murray added the comment: The Sauce labs option may render this obsolete, but to answer your question, Russell: our buildbot fleet is distributed in many people's offices, basements, and occasionally colo racks. The buildbot needs to be on-line 24/7, but it "calls out" and does not n

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Nick: Finding a way to get on-device test results is next on my TODO list, once I've got the patch up to date for trunk. FYI - Updating to trunk is currently blocking on issue22625 (which was introduced by the fix for issue22359). I had thought about us

[issue23670] Modifications to support iOS as a cross-compilation target

Nick Coghlan added the comment: (Some work on the Buildbot site would still be required, but it would be triggering a Sauce Labs run rather than managing the mobile hardware directly) -- ___ Python tracker ___

[issue23670] Modifications to support iOS as a cross-compilation target

Nick Coghlan added the comment: Rather than trying to do something ourselves on the mobile testing front, we may want to instead explore the free-for-open-source-project offering from Sauce Labs: https://saucelabs.com/opensauce/ Adapting that to run the CPython self-tests as an "app" might be

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Understood that buildbots are required. The subject has come up a couple of times on mobile-sig - however, I haven't got a good answer for exactly what this means in practice. Does build hardware need to be delivered to a specific build farm location, or

[issue23670] Modifications to support iOS as a cross-compilation target

R. David Murray added the comment: Also remember that being a supported platform requires buildbots. If I'm reading this right that means two: one for the simulator build, and one that actually runs on the device (once the run-the-test issues is solved). I'm not sure what would need to be do

[issue23670] Modifications to support iOS as a cross-compilation target

Ned Deily added the comment: A thought, primarily as a note to myself for further investigation: the current OS X framework build support and, to a lesser extent, universal build support have added a fair amount of special-case cruft to the build process, primarily in configure.ac and the main

[issue23670] Modifications to support iOS as a cross-compilation target

Ned Deily added the comment: Ack, much to consider. Adding doko as I believe he has been most closely following developments with libffi releases. -- nosy: +doko ___ Python tracker ___

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Nick: you are correct - these are changes to support iOS as a cross-compilation target, so you can run your Python code on an iOS device. Apologies for the confusion in nomenclature. Ned: You're correct that the build needs to be run on an OS/X machine, a

[issue23670] Modifications to support iOS as a cross-compilation target

Ned Deily added the comment: As a cross-compilation target. From a first quick look at it, it appears the patch requires a current Mac OS X system to build for iOS; the necessary standard build tools and SDKs for iOS are only available on OS X. These are the same build tools used for OS X bui