3 ms·
I don't know, considering that the only reason you can't compile an application targetting MacOS from your Linux CI/CD is a license that disallows the use of ce
by apatheticonion 3y ago
I don't know, considering that the only reason you can't compile an application targetting MacOS from your Linux CI/CD is a license that disallows the use of certain MacOS libraries from being used outside of MacOS - combined with Apple's history of aggressively ring-fencing their users, it's understandable that engineers would feel that it's deliberate.
If you copy those libraries illegally to Linux, you can build for MacOS from Linux - so either Apple feels indifferent towards engineers building for MacOS or they want everyone to buy a Mac and compile release software locally.
What worse is Apple doesn't provide any server-specific hardware/software for automation - so it really does feel like Apple expects people to build release software on MacBook Pros or something.
- Someone 3y ago> a license that disallows the use of certain MacOS libraries from being used outside of MacOS It doesn’t make a big difference in practice, but is there such a clause in their license? I thought the limitation was on Apple hardware. If so, you can build on Linux running on a Mac mini, for example.
- apatheticonion 3y agoI believe it's a) on Mac hardware and b) on MacOS (or a VM running on top of MacOS - can be any OS if virtualized) The same terms cover usage of things like Rosetta 2, which cannot be used on Asahi Linux despite Linux running on Mac hardware.