From: Paul H. <pmh...@gm...> - 2013-08-16 16:30:10
|
On Fri, Aug 16, 2013 at 9:08 AM, Chris Barker - NOAA Federal < chr...@no...> wrote: > On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <md...@st...> > wrote: > > We actually discussed this very issue yesterday in our Google hangout > about > > continuous integration. We're probably going to need to script a full > setup > > from a clean Mac + XCode to a working matplotlib development environment > in > > order to make that happen, > > Just a note -- this did NOT "just work" the other day for me -- it > found the freetype libs that OS-X has in the X11 build, but didn't > like them at compile time. I haven't debugged it yet, sorry. > > But the real trick here is what you want to build: which OS-X versions > do you want to support? which architectures? which Python Build(s)? > > What I've been planning on doing is setting up a gitHub (or something) > project for building the various dependencies that various python > packages need -- there are a few that are broadly used: libpng, > libfreetype (used by MPL, PIL, wxPython, ???). The idea is that if you > wanted to build MPL (or PIL, or ???) you'd grab the > MacPyton_Dependencies project, build it, then go from there. > > Anyone want to help? It just feels like we are all repeating > each-others work a LOT here! > > NOTE: the big issues come up if you want to build binaries that are > re-distributable (as a package, or with py2app, or???). In this case, > you need binaries that can run on perhaps older machines than the one > you're building on, or a different architecture. Building to run on > the machine it's built-on is a lot easier. (particularly with macport > or homebrew) > > -CHB Wow! Ambitious. I'll try to keep track of this and help out where possible. Side note: it'll probably be good to alert the pandas folks to such a project. I feel like they're always on Macs at their presentations. They probably have some good ideas for this stuff. -p |