4 ms·

> I also had plans to port to Mac OS X, but like with PS2, this proved too difficult since I was unable to install a working C compiler and development environm

by lloeki 8y ago

> I also had plans to port to Mac OS X, but like with PS2, this proved too difficult since I was unable to install a working C compiler and development environment on Mac OS X. I am surprised by this statement, as it's generally as easy as xcode-select --install to install the CLT (or failing that, installing full-blown Xcode). Slightly up in the article there is mention of Lion, so maybe this is related.

deleted 8y ago
[deleted]
roblabla 8y ago
While this is true, I have a few major gripes with the toolchain that comes with XCode. For instance, I was recently working on a project using C++17 features. It works correctly on linux and windows, but making it compile on macOS was nigh impossible. The clang compiler that comes bundled with macOS has a "special" version that makes it very hard to know where exactly it stands compared to the normal LLVM repository. Then there's the problem of libraries. You have to use homebrew or whatever to install libraries in /usr/local. Some libraries would conflict with the system though, so you have to fiddle with env variables to make the build system find it. Overall, building on MacOS/Xcode is a frustrating experience. I ended up installing nixos and using its toolchain for my work...
- twodayslate 8y ago
  The documentation for the macOS version of clang seems to be non-existent as well (sans the man/info page - but even that seems incorrect as some flags simply don't work).
deleted 8y ago
[deleted]
jagger27 8y ago
brew install gcc@8 Yeah this part confused me as well.
- nategri 8y ago
  had brew utterly let me down for gdb recently. had to compile from source and then code sign it. nightmare mode.
  - xyzzy_plugh 8y ago
    That's not really brew's fault -- but perhaps they could streamline this process? OSX requires binaries to be signed to give them tracing/debugging privileges (or you can use root). It would be nice if Apple made this less painful -- or rather, if they stopped making native development increasingly more painful with every OS release.
    - nategri 8y ago
      agreed. if it's anyone's fault, it's apple's. that's a helluva lot of friction to install a nigh-ubiquitous dev tool.
      - lloeki 8y ago
        > if it's anyone's fault, it's apple's. I'm quite glad random unsigned binaries don't have the right to unilaterally attach to (signed) processes, otherwise the signature would be moot.

by lloeki 8y ago

deleted 8y ago

[deleted]

roblabla 8y ago

While this is true, I have a few major gripes with the toolchain that comes with XCode. For instance, I was recently working on a project using C++17 features. It works correctly on linux and windows, but making it compile on macOS was nigh impossible. The clang compiler that comes bundled with macOS has a "special" version that makes it very hard to know where exactly it stands compared to the normal LLVM repository. Then there's the problem of libraries. You have to use homebrew or whatever to install libraries in /usr/local. Some libraries would conflict with the system though, so you have to fiddle with env variables to make the build system find it. Overall, building on MacOS/Xcode is a frustrating experience. I ended up installing nixos and using its toolchain for my work...

twodayslate 8y ago
The documentation for the macOS version of clang seems to be non-existent as well (sans the man/info page - but even that seems incorrect as some flags simply don't work).

deleted 8y ago

[deleted]

jagger27 8y ago

brew install gcc@8 Yeah this part confused me as well.

nategri 8y ago
had brew utterly let me down for gdb recently. had to compile from source and then code sign it. nightmare mode.
- xyzzy_plugh 8y ago
  That's not really brew's fault -- but perhaps they could streamline this process? OSX requires binaries to be signed to give them tracing/debugging privileges (or you can use root). It would be nice if Apple made this less painful -- or rather, if they stopped making native development increasingly more painful with every OS release.
  - nategri 8y ago
    agreed. if it's anyone's fault, it's apple's. that's a helluva lot of friction to install a nigh-ubiquitous dev tool.
    - lloeki 8y ago
      > if it's anyone's fault, it's apple's. I'm quite glad random unsigned binaries don't have the right to unilaterally attach to (signed) processes, otherwise the signature would be moot.