On 20.05.2007, at 10:02, Boey Maun Suang wrote:
./CXX/Extensions.hxx: In constructor 'Py::PythonExtension<T>::PythonExtension() [with T = FuncXY]': src/_transforms.h:466: instantiated from here ./CXX/Extensions.hxx:477: warning: right-hand operand of comma has no effect
These warnings I am not too worried about...
but a friend of mine said that errors like this"
src/_wxagg.cpp: In function 'wxBitmap* convert_agg2bitmap (RendererAgg*, Bbox*)': src/_wxagg.cpp:238: error: conversion from 'wxImage*' to 'const wxString' is ambiguous /opt/local/include/wx-2.8/wx/string.h:692: note: candidates are: wxString::wxString(wxChar, size_t) <near match> /opt/local/include/wx-2.8/wx/string.h:682: note: wxString::wxString(int) <near match>
are usually a sign that the overloaded function (which here is wxString::wxString) does not have an overloading whose arguments are of the right number type.
yup. From the C++ perspective that could be right, but that's not where I want to get at. I want py-matplotlib to work... Ok, here's I propose to proceed: I implemented a wxpython variant and make sure that wxpython (WXAGG) is used if the user specifies this variant, but is definitely switched off otherwise (circumventing matplotlibs auto-detection). I have changed the gtk2 variant to behave the same way (it did already for GTKAGG, but not for GTK). py-matplotlib builds with either variant, but with wxPython it crashes upon "import pylab". I will report the problem upstream. Anyway, that's what I get when building against wxPython: DEBUG: Assembled command: 'cd "/opt/local/var/db/dports/build/ _Users_jochen_source_macports-trunk_dports_python_py-matplotlib/work/ matplotlib-0.90.0" && /opt/local/bin/python2.4 setup.py build' setup.py:267: DeprecationWarning: The wxPython compatibility package is no longer automatically generated or actively maintained. Please switch to the wx package as soon as possible. import wxPython /opt/local/lib/python2.4/site-packages/wx-2.8-mac-unicode/wx/_core.py: 13967: UserWarning: wxPython/wxWidgets release number mismatch warnings.warn("wxPython/wxWidgets release number mismatch") WXAgg's accelerator requires wxPython running build Seem to confirm my previous thoughts on version mismatch and looks like a real upstream change is necessary;( I will check in the current version, although the wxPython variant is broken. But that is better than the old Portfile, which would always be broken if current wxPython is installed. Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll