3 ms·
A large part of that, from what I've encountered (by no means a representative sample), is due to Unix makefiles expecting/requiring X in specific-location-Y, o
by Groxx 16y ago
A large part of that, from what I've encountered (by no means a representative sample), is due to Unix makefiles expecting/requiring X in specific-location-Y, or making things stringly-typed[1], or outright artificially restricting the systems it thinks it can run on, failing fake sanity checks up-front. Or other bad code.
But yes. OSX is not a direct match to other Unix-like systems, and a lot of source compiles not tweaked to handle OSX (many are) will require changing a couple things. Though Qt worked just fine for me, so who knows.
[1]: http://stackoverflow.com/questions/2349378/new-programming-jargon-you-coined/2444303#2444303 http://stackoverflow.com/questions/2349378/new-programming-j...
- vog 16y ago> A large part of that, from what I've encountered ... Since I was talking about Makefile that run unmodified on any BSD and Linux, I'm clearly not talking about the kind of crappy build scripts you are mentioning. Those are an issue of their own. > a lot of source compiles not tweaked to handle OSX The problem is that you have to tweak scripts. You have to tweak even clean, simple scripts or libraries that use only portable constructs (i.e. without any hard-coded paths and other stupid stuff). And that's really nasty.
- jammur 16y agoWhat experience is this based on? In my 6 years experience using a Mac as my primary machine, I've never had a higher rate of problems installing open source software with the default build scripts than on Linux. Also, there's Macports, Fink, and Homebrew, which make it effortless.
- jonhohle 16y agodo you have an example of something that compiles cleanly on FreeBSD that doesn't in OS X?