I am running 10.10.1 and 10.10.2 (pre-release, for development reasons), and I can’t see artifacts in either of those. Also, from the build logs you posted, I see you’re on OS X 10.10. I certainly understand if you would prefer not to share this information, but if you don’t care, it would be helpful to know which model of mac you are on. Otherwise, it would seem to be a bug specific to certain versions of OS X or GPU hardware, which is probably something we need to track down. It’s possible it was a bug specific to the revision that the repo was at when you built it, and and has since been fixed.

I am working on making it reuse the patched wx files, but it will be a bit until that’s I am unable to reproduce those artifacts on my machine. Unfortunately, it will still be a lengthy build every time, for now. This will upgrade it without wasting time on the library, which is updated every time you access it in KiCad (which is awesome! And why its on github!). Also, homebrew doesn’t know to update -HEAD formula, so if you want to move up to a newer revision, you will want to run brew reinstall kicad -HEAD -without-kicad-library. You can link to it manually too, all the binaries are located under /usr/local/lib/libcairo*.Īnyway, good luck. However, if you don’t need it as a framework, the version installed by homebrew is fine and tools like autotools or cmake will find and link to it without issue.

That is what the missing symbols error was saying - that needed 64-bit code in Cairo weren’t there. The one you have is 32-bit only, but building under Yosemite requires linking to 64-bit AND 32-bit, or 64-bit only, anything 32-bit only cannot be used.

I am not sure where it came from, but if you need to use it in framework form, I would recommend seeing if you can find (or build) the most recent version, and make sure to make it universal so it includes 64-bit code in the framework. In fact, the website recommends using a package manager (like mac ports, fink, or homebrew) to install cairo, as it will be built as a dylib and installed where programs can find it. Great! By the way, Cairo does not provide a framework for OS X anymore, and the supported usage is by building.

Homebrew xcode