Re:Mac OS X Leopard and Xcode on iPad Pro
by toyg on Saturday June 20, 2020 @05:52AM
(#23582939)
Ish. It’s like you’re staying at this wonderful hotel that is very expensive and you absolutely love, but they refuse to allow wifi in the rooms. So you rig up your own hacky solution to get wifi anyway, hoping they won’t discover it and throw you out.
Re:Mac OS X Leopard and Xcode on iPad Pro
by solarkraft on Saturday June 20, 2020 @07:49AM
(#23583401)
I have a feeling that this is what's coming, but they're taking their time to do it well. It would absolutely be the right kind of halo-app to promote (and engineer a good solution for) Apple OS convergence.
Re:Mac OS X Leopard and Xcode on iPad Pro
by hellofunk on Saturday June 20, 2020 @04:44AM
(#23582676)
It would definitely be very nice to have a keyboard attached to an iPad running Xcode, and when you want to run your iPad app it just launches on the device like when you’re developing a Mac app on the Mac. That would be excellent.
Re:Mac OS X Leopard and Xcode on iPad Pro
by messe on Saturday June 20, 2020 @09:04AM
(#23583711)
If you're going down that route, a VPS is an alternative (albeit more expensive) option. Blink shell is a great ssh/mosh client, and code-server makes for a great IDE.
Re:Mac OS X Leopard and Xcode on iPad Pro
by saagarjha on Friday June 19, 2020 @10:25PM
(#23580983)
I’m curious if there’s an iPad old enough to be supported by Xcode while also new enough to run UTM so you can actually use Xcode to build an app that could theoretically run directly on the device.
Re:Mac OS X Leopard and Xcode on iPad Pro
by jsjohnst on Saturday June 20, 2020 @01:06AM
(#23581850)
Tweet thread seemed to imply Xcode 3.1.4 was being used. I think you needed Xcode 3.2 to target the first gen iPad (which is Snow Leopard or higher as you mentioned). While UTM wouldn’t probably work on it, I did get Bochs running on the first gen iPad and booted Windows 95 (albeit it took 45min to start and the iPad felt like a hot plate), so I wouldn’t say impossible, just very very unlikely.
Re:Mac OS X Leopard and Xcode on iPad Pro
by Wowfunhappy on Saturday June 20, 2020 @09:56AM
(#23583949)
Well, it never officially did. From the Macintosh Garden page I linked:
> Despite Apple's claim that the SDK was available for Intel Macs only, some clever developers soon realized that all the frameworks and programs the SDK delivered were compiled as Universal (PPC/Intel) code while the compiler configuration files were ARM/Intel only. Moreover the installer checked for Intel architecture and denied installation on PPC Macs. Installing the .pkg archives manually and repairing the compiler configurations made the iPhone SDK run completely on PPC Macs.
Re:Mac OS X Leopard and Xcode on iPad Pro
by callalex on Saturday June 20, 2020 @01:45AM
(#23582011)
If we can get to the point of EMULATING a whole-@$$ computer on the device, maybe, just maybe, that device was slightly capable of running a compiler a looooooooooooooooong time ago.
Re:Mac OS X Leopard and Xcode on iPad Pro
by dgl on Saturday June 20, 2020 @04:56AM
(#23582726)
There are compilers on the App Store, e.g. https://holzschu.github.io/a-Shell_iOS/ — however it’s compiling to WebAssembly and then running that, but the compiler is still native...
Re:Mac OS X Leopard and Xcode on iPad Pro
by jsjohnst on Saturday June 20, 2020 @04:50PM
(#23587182)
As said in another reply thread[0], I booted Windows 95 on a first gen ipad almost a decade ago using bochs, hence the sarcasm re: Xcode finally being the proverbial straw for GP.
Re:Mac OS X Leopard and Xcode on iPad Pro
by josteink on Saturday June 20, 2020 @03:02AM
(#23582326)
But to run a compiler you’d have to be able to see files, and as we all know, Apple-customers find things like that very, very scary.
Edit: I’m sarcastically referring to Apple’s original justification for not making files a concept on iOS, and thus I’m mocking Apple’s condescending judgement of its own users, not the actual users themselves. I thought that much would be obvious.
Re:Mac OS X Leopard and Xcode on iPad Pro
by thebruce87m on Saturday June 20, 2020 @09:29AM
(#23583818)
It might benefit you to highlight your sarcasm. This will help when readers of your comment aren’t native English speakers, or when your sarcasm is sub par.
Something like:
That was a solid whoosh. Good one. You really got me there. /s
Re:Mac OS X Leopard and Xcode on iPad Pro
by jbverschoor on Saturday June 20, 2020 @04:01AM
(#23582540)
Would loooooove to have an iPad Pro em for most of my stuff and have the ability to use a fast VM for development or other things that require me to have more control and finegrained window management
Re:Mac OS X Leopard and Xcode on iPad Pro
by villgax on Saturday June 20, 2020 @02:16AM
(#23582142)
There needs to a shift in the way Xcode deploys apps or iOS accepts over WiFi app installs, only then can Xcode as an App rather than a VM help with development on the device you are actually using even if it cannibalises Mac sales.
Re:Mac OS X Leopard and Xcode on iPad Pro
by hellofunk on Saturday June 20, 2020 @04:46AM
(#23582684)
iOS does accept Xcode builds over Wi-Fi, in case you weren’t already aware. I think that’s how most people work now, when they run the project in Xcode, it just launches on the iOS device wirelessly.
Re:Mac OS X Leopard and Xcode on iPad Pro
by burgerzzz on Sunday June 21, 2020 @06:35AM
(#23591194)
I’m sooo ready to work on my web apps on my iPad Pro with the magic keyboard. It really feels like it could be an great developer experience if we could just run/build Node apps.
Re:Mac OS X Leopard and Xcode on iPad Pro
by exabrial on Saturday June 20, 2020 @09:38AM
(#23583864)
I'm not sure we'll ever see a full xcode release for iPad unless something drastic happens with the way mobile operating systems work. On your desktop you are king, you have the freedom to delete most every file or install any utility to any directory. Apple does not want you to have that autonomy on your devices and made sure from the start that you are unable to do anything unless they approve. I just don't see a marriage between these two worlds anytime soon.
Re:Mac OS X Leopard and Xcode on iPad Pro
by zepto on Saturday June 20, 2020 @09:52AM
(#23583929)
For a full release you are probably right, but a release that can only build iOS apps with swift and swiftui would be quite easy for them at this point.
Doing hacky things on Apple products seems pointless in my opinion, because people paid their way into a walled garden that are now trying to escape?
Free your talent and creativity by putting your effort into open platforms.
I’d like to see Xcode —in full, and up to date— running on an iPad.
At that point, iPad will suddenly become a viable development platform, and one I would definitely consider using as a traveling system.
That's a really big job, and they can't afford many screw-ups.
[0]: https://twitter.com/jon_prosser/status/1252931201708560385
Blink shell: https://blink.sh/
code-server: https://github.com/cdr/code-server
For testing big builds or anything you want some power for, a good way to go when you need portability.
Technically you can compile iOS stuff on Linux or jailbreaked iOS, all you need is clang and apple toolchain. Examples: https://github.com/theos/theos/wiki or https://github.com/tpoechtrager/cctools-port/
So, I'm going to go ahead and say it's impossible.
> Despite Apple's claim that the SDK was available for Intel Macs only, some clever developers soon realized that all the frameworks and programs the SDK delivered were compiled as Universal (PPC/Intel) code while the compiler configuration files were ARM/Intel only. Moreover the installer checked for Intel architecture and denied installation on PPC Macs. Installing the .pkg archives manually and repairing the compiler configurations made the iPhone SDK run completely on PPC Macs.
[0] https://news.ycombinator.com/item?id=23579974
Edit: I’m sarcastically referring to Apple’s original justification for not making files a concept on iOS, and thus I’m mocking Apple’s condescending judgement of its own users, not the actual users themselves. I thought that much would be obvious.
Something like:
That was a solid whoosh. Good one. You really got me there. /s
It would only use Swift and SwiftUI, and only target iOS.