I've consistently been able to build matplotlib on OS X. Just make sure you have all the dependencies installed. Personally, I have lbpng and whatnot installed in /usr/local instead of /usr/X11. I don't know if that'll help. Also, I use the GCC 4.2 that Apple has available for download on developer.apple.com. Then you just change the Makefile in the /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/ directory to not use Wno-long-double or no-cpp-precomp. I also took out all the ppc arch flags since it was causing some issues there with my versions of libpng and whatnot technically not being universal binaries. If you don't want to build univeral binary versions of your dependencies or use the ones alread provided in /usr/X11 (which are universal I think), you should make Python only build for your architecture, which is what I did.
My only issue with matplotlib thusfar seems to be the inability to do the plot3d examples from the scipy website, but I'm told that stuff is officially unsupported anyway. Josh On Wed, May 28, 2008 at 3:35 PM, Eric Firing <[EMAIL PROTECTED]> wrote: > Christopher Barker wrote: >> Tommy Grav wrote: >>>> I >>>> don't know that it has ever all been consolidated into one easy-to- >>>> find, easy-to-use set of instructions that will work for just about anyone. >> >> no, it hasn't. > And one of the reasons may be that it is very complicated in practice, > with all the possible variations of OSX versions, Xcode versions, > processor architectures, and styles of build for python itself and > various libraries. It seems to require learning a whole new jargon. >> >> However, I think: >> >> $ easy-install matplotlib >> >> should work, at least with the python.org python2.5 >> >>>> Maybe someone can provide, or has provided, a universal binary of >>>> 0.91.2 built against numpy 1.1? >> >> does it need to be "built against" numpy at all? I didn't think it was a >> build-time dependency -- that is, any MPL 0.91.2 should do, and you can >> drop a new numpy into it. I don't know if there is one yet, though... > > _backend_gdk.c and nxutils.c both call into the numpy C API; maybe some > c++ code does also. It is not entirely clear to me whether 1.1 is > sufficiently binary-compatible that this is safe. > > >> There are essentially two options: >> >> 1) built it just for yourself -- I think the instructions John H. posted >> are pretty easy to follow. > > That's the way they look, but having watched someone try it, I can > testify that looks are deceptive. I would say that with 95% > probability, if Tommy tried to follow John's instructions, he would not > succeed. > > Eric > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
