On Wed, May 24, 2017 at 7:37 AM, H. William Welliver III <[email protected]> wrote: > I’ve been quietly working on this for a few weeks now, and have got the > various permutations working on OS X. Basically, there are 2 paths for GTK > on OS X (now called macOS): X11, which is the classic approach, and Quartz, > which is native, but newer and a little less fully baked. Homebrew, a very > popular package manager on OS X, switched to Quartz mode at some point, > which broke the pike builds. This sort of dual mode situation affected GL > and GLUT as well. So, I’ve arrived at a solution where we prefer the native > Quartz versions but will fall back if they’re not present (such as if you > happen to be running the Darwin open source OS that macOS is based on. I > think that’s the most reasonable approach because every macOS install will > have Quartz, GL and GLUT (and using GTK doesn’t require you to install > X11/XQuartz.
Just managed to borrow someone to do some testing for me on a Mac, and here's what we found: 1) Homebrew is pouring bottles of Pike 7.8.866. I would very much like to change that at some point, but have no idea what that entails. How do you bottle a formula? 2) Building Pike from source crashes out checking if rusage.c works in CONFIGURE_TEST mode. 3) rusage.h was not found. I don't know if that's significant. Testing was done with the latest in the 8.1 branch, commit 3cc5d04. I've successfully run a clean build of that same commit on my Linux box, so it's not a critically broken commit or anything. Sadly, I don't have a Mac to do any testing on, so I can't actually probe this at all. What's the recommended way to install (a) a recent stable Pike, and (b) the latest dev Pike, on a Mac? I much appreciate the work being put into this. Pike + GTK2 should mean we can do cross-platform GUIs easily... but it's not an easy thing to accomplish. ChrisA
