Live data from Hacker News

Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

github.com

51–60 of 76 posts

Re: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

#52
post #14

The problem with this is licensing: the macOS SDK license says that it's only to be used on an "Apple-branded computer". That said I wonder what Apple would do if this is used outside of that case...

I used a Hackintosh for a number of years and Apple could have easily shut down the entire community with enough cease and desists. In fact there were engineers that helped provide valuable information.

They don't mind what people do for personal use. Just don't try and turn it into a commercial product.

Re: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

#54
post #14

The problem with this is licensing: the macOS SDK license says that it's only to be used on an "Apple-branded computer". That said I wonder what Apple would do if this is used outside of that case...

Sounds like that would allow a Linux VM running on a macbook

Re: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

#55
post #30

Earlier quoted context omitted.

Which is why they changed the wording from "Apple-labeled" to "Apple-branded" around the time of Snow Leopard IIRC.

How much could a branding iron cost?

This place [0] sells custom design branding irons starting at $93.

0: https://brandingirons.com/products/basic-fire-heated-brandin...

Re: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

#56

Earlier quoted context omitted.

Interestingly you can use zig within your Rust build to more easily cross-compile: https://github.com/rust-cross/cargo-zigbuild I’m curious what the blockers are for rustc to cross-compile like zig does natively.

Just add another arch with rustup. Am I missing something?

I could be mistaken, but I believe that installs a completely parallel toolchain which is relatively large compared with zigs approach of having all the platforms generatable from a single toolchain.

Re: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

#57
post #33

Earlier quoted context omitted.

Why is this a defense for them using the labor of non-consenting artists to generate a crappy header image? Surely they could ask an artist to volunteer their time just as they volunteered theirs?

> Surely they could ask an artist to volunteer their time just as they volunteered theirs? Unfortunately "I spent a lot of time on this thing you have no interest in or relation to" is not a very convincing argument in the FOSS world.

> not a very convincing argument

Neither is "I'm not going to contribute a damned thing, but nonetheless the team behind this free product needs to spend more time and/or money to make me happy."

If you don't like the logo, well... that sounds a lot like a personal problem to me.

Re: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

#58

Earlier quoted context omitted.

Interestingly you can use zig within your Rust build to more easily cross-compile: https://github.com/rust-cross/cargo-zigbuild I’m curious what the blockers are for rustc to cross-compile like zig does natively.

Just add another arch with rustup. Am I missing something?

Rustup arch only adds support for static libraries (unliked objects), and craps out as soon as you try to build a binary.

Rust did not do the legwork that zig did to bundle libc and a working linker, and Cargo is exceptionally naive in its default configuration, so it won't even find a usable cross-linker on the system, nor even try the chronically-unfinished rustc-lld integration there is.

Re: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux

#59

I think the project can easily add Go to the list as cross compiling is built-in: GOOS=darwin GOARCH=arm64 go build -o bin/app-silicon-darwin app.go

I've been using goreleaser-cross for cross-compiling Go apps with cgo https://github.com/goreleaser/goreleaser-cross
Post reply on HN