Re: [Matplotlib-users] build matplotlib including backend wxPython

2008-01-23 Thread Matthias Michler
Hello Ken, Hello Mike, Hello all, On Tuesday 22 January 2008 19:33, Ken McIvor wrote: On Jan 22, 2008, at 11:00 AM, Matthias Michler wrote: I was not up to date with my installation and I tried to use the latest svn version (trunk) on my Debian etch. I have a problem to build matplotlib

Re: [Matplotlib-users] build matplotlib including backend wxPython

2008-01-23 Thread Christopher Barker
Just another note: If you can use wxPython 2.8.*, then this problem should go away. 2.8 added some methods that allow more directly moving bitmaps from Agg to wxPython, eliminating the need for any extension code. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response

Re: [Matplotlib-users] build matplotlib including backend wxPython

2008-01-22 Thread Michael Droettboom
This is a known bug in the Debian packaging of wxPython. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326440 There are some workarounds mentioned in that post. Personally, I usually end up building wxPython from source (which doesn't have this header file problem) to keep up with its

Re: [Matplotlib-users] build matplotlib including backend wxPython

2008-01-22 Thread Ken McIvor
On Jan 22, 2008, at 11:00 AM, Matthias Michler wrote: I was not up to date with my installation and I tried to use the latest svn version (trunk) on my Debian etch. I have a problem to build matplotlib including support for wxPython as backend. The output is attached below. Actually