| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
include instructions for users of packaging systems (e.g. MacPorts).
|
+1 from me. The discussion on #168 is the relevant background information. |
Sorry, something went wrong.
|
Not having it look for fink and macports packages is fine - if you have one of those you can just use their matplotlib packages. |
Sorry, something went wrong.
|
@jdh2358: I have been able to test this successfully on OSX 10.7 with both homebrew and apple Python 2.7. @r-owen has tested on 10.6. Do you know who else should see this before I commit? @efiring: I know you were involved in the original discussion. Do you have any objections to this change? |
Sorry, something went wrong.
|
No objection. Let's try it and see what happens. |
Sorry, something went wrong.
|
+1 (though cannot test now, travelling) I think the big reason for recommending make.osx is all the build problems you get when setupext picks up incompatible versions of libraries, so reducing the number of directories it looks in should help. I think if /usr or /usr/X11 has a version of freetype that's incompatible with /usr/bin/python, it's an Apple bug, but people could have installed whatever libraries in /usr/local (perhaps indirectly - .pkg installers can leave stuff all over your system). Does the output from "python setup.py build" indicate which directories each dependency is found in? That information could help when people report build problems. |
Sorry, something went wrong.
No. But it looks like the setupext could be made to do so with a bit of effort if we did want that ability. I'm going to merge this issue, but will open a subsequent issue for getting the path info for some of the build dependencies. |
Sorry, something went wrong.
Updated setupext.py that allows building on Mac OS X
| Back | FazBrowse Home | New Git URL |
Fix build on Mac OS X so that:
This new setupext.py will not work with MacPorts or fink, but the old one would not either. I think it is dangerous to try to support both by default, since old or incomplete setups could lead to including unexpected libraries.