> This project is a fork of the official QEMU repository Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
What do you mean?
iOS on QEMU
31–40 of 106 posts
Re: iOS on QEMU
#32Re: iOS on QEMU
#33This would be interesting to see, I'm guessing the implications are being able to build iOS projects without requiring a Mac at any stage of the development process.
You can actually do this now, without emulation: https://github.com/tpoechtrager/cctools-port Zig are also working on it: https://zig.news/monthly/zig-monthly-august-2021-ios-support... The pioneer of software dictatorship will probably make this impossible or illegal as soon as it gains any traction though. And people will probably congratulate them for it in the name of "security".
As a “closed iOS” advocate, I personally believe the ability to do development outside of a macOS is a great idea. I’ve long wanted to make iOS apps, but I don’t have the money to shell out for a Mac. Yes, Hackintoshes are a thing, but you need certain hardware to do so, and even then, it’s still difficult (last I checked).
Re: iOS on QEMU
#34> This project is a fork of the official QEMU repository Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
This is _actually_ a fork. A fork is a separate repository sharing history with another.
The GitHub UI's concept of a "fork" is unrelated to Git. GitHub doesn't detect you made a proper fork if you don't use its API or UI to do so, and requires contacting customer support to change it.
Not worth the hazzle as it provides no benefit.
Re: iOS on QEMU
#35WOW! That's insane. If made efficiently enough, you could emulate iOS on a non-iOS mobile device. That would be disruptive.
And also very easy to brake on apple's end.
Only for future releases. If it works currently for iOS 12, it'll keep working for those builds of iOS 12. I fail to see how Apple can break what already works for code they can't/won't change.
Re: iOS on QEMU
#36> This project is a fork of the official QEMU repository Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
> Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
From Wikipedia:
In software development, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software.
This seems exactly what happened here.
Are you asking why they didn't use Github's "fork" mechanism?
Github's "fork" mechanism creates a relationship between the two repositories that the developers of this software may not want. For example if the "upstream" ever becomes unavailable, all Github "forks" are auto-deleted. This is surprising to some people and definitely not what an independent separate development would want.
Re: iOS on QEMU
#37Earlier quoted context omitted.
You can actually do this now, without emulation: https://github.com/tpoechtrager/cctools-port Zig are also working on it: https://zig.news/monthly/zig-monthly-august-2021-ios-support... The pioneer of software dictatorship will probably make this impossible or illegal as soon as it gains any traction though. And people will probably congratulate them for it in the name of "security".
As a “closed iOS” advocate, I personally believe the ability to do development outside of a macOS is a great idea. I’ve long wanted to make iOS apps, but I don’t have the money to shell out for a Mac. Yes, Hackintoshes are a thing, but you need certain hardware to do so, and even then, it’s still difficult (last I checked).
For casual app development I just run MacOS in a free VMWare instance on my Windows machine. It has no graphics acceleration but otherwise works flawlessly.
Re: iOS on QEMU
#38> This project is a fork of the official QEMU repository Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
What do you mean?
I'm assuming they mean it wasn't forked by clicking the "fork" button in GitHub, which creates a link at the top of the new forked repository page connecting it to the parent repository.
It is a true fork though, both projects have the same commit history.
Re: iOS on QEMU
#39> This project is a fork of the official QEMU repository Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
This is _actually_ a fork. A fork is a separate repository sharing history with another. The GitHub UI's concept of a "fork" is unrelated to Git. GitHub doesn't detect you made a proper fork if you don't use its API or UI to do so, and requires contacting customer support to change it. Not worth the hazzle as it provides no benefit.
Also, QEMU upstream isn't on Github, so the notion is even more pointless.
Re: iOS on QEMU
#40> This project is a fork of the official QEMU repository Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
I read a blog post a few years back discussing some issues with Github's fork feature (as opposed to just creating a new repo that isn't explicitly linked to the original within Github's UI). From a quick search, I believe this[1] was it, and I remember finding it fairly compelling.