On Fri, Mar 8, 2013 at 3:46 PM, Tejashri Kandolkar <
tejashri.kandol...@gmail.com> wrote:
> Thanks Christoph, thanks for the help.
>
> However I found the issue.
> The issue is that somehow matplotlib_release variant linked to the debug
> lib of libpng.
> And so on a non-developer machine, which d
On 3/7/2013 8:39 AM, Christoph Gohlke wrote:
> On 3/7/2013 6:00 AM, Tejashri Kandolkar wrote:
>> Hi,
>>
>> I built matplotlib1.2.0 with python3.2 on Windows7 from source.
>> I built the libpng and freetype libs and linked them statically to
>> matplotlib.
>>
>> Everything works fine on my machine,
On 3/7/2013 6:00 AM, Tejashri Kandolkar wrote:
> Hi,
>
> I built matplotlib1.2.0 with python3.2 on Windows7 from source.
> I built the libpng and freetype libs and linked them statically to
> matplotlib.
>
> Everything works fine on my machine, I can run the matplotlib examples etc
> But on a new W
Hi,
I built matplotlib1.2.0 with python3.2 on Windows7 from source.
I built the libpng and freetype libs and linked them statically to
matplotlib.
Everything works fine on my machine, I can run the matplotlib examples etc
But on a new Win7 machine(with the exact same configuration as mine, except
