On 8/16/2011 11:12 PM, Eric Firing wrote: > On 08/16/2011 10:10 AM, John Hunter wrote: >> On Mon, Aug 15, 2011 at 9:34 PM, Benjamin Root<ben.r...@ou.edu> wrote: >>> The mpl developers are getting very close to the long-awaited v1.1.0 release >>> of matplotlib. Before we do so, we are doing some final checking of the >>> documentation to make sure that all critical pieces of information iss >>> correct and up to date. >>> >>> In checking over the instructions for building and installing matplotlib on >>> MacOSX, I have found two separate sets of instructions. On the install >>> page, there is a reference to a README.txt file in "release/osx". This file >>> is there, but it seems to refer to other files that no longer exists. >>> Meanwhile, there is an un-referenced file in the top directory called >>> README.osx that seems a lot more current. >>> >>> Because I do not have a Mac that I can use for development, I would like to >>> ask the community for help in determining the correct set of instructions >>> and to eliminate cruft. I think it would also be useful to point users to >>> any relevant instructions for installing/building numpy on Macs. I would >>> also like to make sure we are current with information on installing on a >>> stock Lion install. >>> >>> Please feel free to respond on this list, or better, make a branch on github >>> and submit pull requests to help us improve these documents. >> >> I wrote both of those files originally (make.osx and releases/osx/*). >> The original division of labor was the stuff in "releases" was >> designed to build the release binaries, and the stuff in make.osx was >> primarily used to build from svn or src. Overtime, most of the effort >> has gone into make.osx, and it now includes support for binaries. I >> no longer build the OSX binaries (Russell does) and no longer use OS X >> (back to ubuntu) so if Russell is not using the stuff in releases/osx, >> we can flush it. > > The releases/win32/ tree is also unmaintained since 0.99.0.rc1. Who > does the Windows builds these days? Christophe? > > It would be nice to have a maintained record of how release builds are > done, or better yet, up-to-date scripts that fully automate it.
IIRC Stan West has updated those build scripts to work with Visual Studio 2008 Express. I use Visual Studio and Windows SDK compilers, whatever is the officially documented and supported compiler by the targeted Python version. I don't use anything from the mpl/releases/win32 tree but follow the instructions at <http://matplotlib.sourceforge.net/users/installing.html> and <http://docs.python.org/distutils/builtdist.html>: run `python setup.py bdist_wininst` after customizing setup.cfg and manually building/installing all required and optional dependencies, making sure they can be found by setup.py (e.g. via environment variables). I don't think it is reasonable or necessary to fully automate this process involving 10 python versions, ~10 dependencies, 4 compilers, and several helper programs (CMake, nasm, git, tar, zip, miktex, Ghostscript). The only thing worth providing might be the prebuilt static link libraries and header files for zlib, libpng, and freetype for the 4 different MSC compilers/runtime libraries. Christoph > > Eric > >> >> JDH > ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
