I'm wary of adding more hard-coded include paths to the system -- it can then be difficult for users to override that when they want to, say, use a locally built copy of freetype.

We could also display a more prominent message when pkg-config can't be found...

You use freetype-config to discover the freetype version, but you don't use it to generate the compile flags, so that's another option. Following the current README.osx will result in a successful "you have freetype 2.4.11", but the compilation will actually fail. freetype-config --libs and freetype-config --cflags should give the relevant info.

Alternate fix would be to search for freetype in the homebrew location

Do we need an alternative fix? It sounds to me like adding pgkconfig to the install list is a good idea...

👍

@minrk, @pelson: I agree that adding pkgconfig to the install list is a good idea in any event, though I also like the suggestion of trying to use freetype-config in addition to pkg-config (I hadn't thought of that, and I think that's a good suggestion). I'll work the latter up as a separate PR, and we can go ahead and merge this one.