To upload games to Steam, devs either go through Steamworks website, or use steamcmd. The web upload on Steamworks website mostly works for small zips, just it is unreliable. At bad times one can stare at the web upload for 10 minutes of failure, errors, "did not receive the entire file" after timeout.

I have finally decided to migrate to upload using steamcmd today. I usually work on a Windows machine and build my game for Windows and Linux. The build and the upload worked flawlessly. It seems steamcmd compares my local build with contents in the depot and only upload some deltas. Saves time and bandwidth.

Until I try to set it up on my Mac. Because of the hellish codesign and notarization, it is better (or less bad) to build everything macOS on a Mac. Then this hits me. > ./steamcmd zsh: bad CPU type in executable: ./steamcmd > file steamcmd steamcmd: Mach-O 64-bit executable x86_64 In comparison, this is Godot: > file /Applications/Godot.app/Contents/MacOS/Godot /Applications/Godot.app/Contents/MacOS/Godot: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64]

I've cursed Apple because Xcode, codesign, notarization are all hell of a maze to navigate, but the expectations of developing a game on a Mac has always been low (at least when you're not developing exclusively for macOS and latest iPhone). I just never thought I'd be mad at Steam. A developer tool, at 2026, under folder `builder_osx`, doesn't support Apple Silicon.

My disappointment is immeasurable and my day is ruined.

Comments URL: https://news.ycombinator.com/item?id=50207196

Points: 6

# Comments: 6