On Tue, Jan 27, 2009 at 4:31 AM, Marcin Krol <mrk...@gmail.com> wrote:
> Hello Patrick,
>
> Thanks for reply!
>
>> I didn't catch on the first email you were trying to build for
>> python2.6.  I haven't been able to get matplotlib to build correctly
>> with python2.6.  I'm actually curious as to how you were able to build
>> matplotlib using the win32_static folder since it doesn't contain the
>> libs and header files for tcl/tk 8.5 which python2.6 is build against.
>
> I didn't do anything really, except I have had installed Python 2.5 on
> the same system before. Maybe this left DLLs lying around and the
> compiled matplotlib uses those old DLLs?
>
>>  This was the original error for me and I had to modify the
>> setupext.py to look for the tcl/tk 8.5 includes (which I had to
>> manually add to win32_static).  What happens if you try:
>>
>> import matplotlib.pyplot as plt
>> x = range(0,100)
>> y = range(0,100)
>> plt.plot(x,y)
>> plt.show()
>
> I have used win32_static_vs (I have VC++ 9.0 installed) and it just
> worked! It displayed the graph and everything.
>
>> As for the error you specifically mentioned, have you checked to make
>> sure that the correct dll exists?  This error typically happens to me
>> when the dll didn't build properly (if at all).
>
> How do I do that? After this successful build, I can't find any DLL in
> the 'build' folder. I have unpacked matplotlib-0.98.5.2.win32-py2.6.exe
> installer and it doesn't contain any dll either.

It might help if you recursively remove the buld directory, do a clean
rebuld, capture the build output in a file, and post that here so we
can see if we can get an idea what is going on

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Reply via email to