Re: [Plplot-devel] Problem builiding the Python bindings on Windows using MS VC/C++

[Arjen M. <Arj...@de...>]

Hi Alan, Andrew,

here are the results for Python on the Windows platform using MSVC/C++ 2010 (32 bits):

- I had to build with the CMake build type set to Release (otherwise a package bug kicks in:
  Python 2.7 inserts a dependency on python27_d.lib which is the debug library that is missing
  from the installation)

- I had to correct a few casts in plplotcmdule.i - MSVC/C++ is pickier than gcc, It seems.

- I had to turn off the Java bindings, as there is something in there MSVC/C++ does not like either.
  I have not looked into that yet.

- Most of the Python examples produce the same results as the corresponding C examples.

- The ones that do not simply crash at some point. These are: 08, 09, 11, 15, 16, 20, 21 and 22.
  I have not looked into the possible cause of this. It may be a single function that is causing this.
  It may be a set of functions.

Anyway, this means that the mystery is only larger: The Python installation was _exactly_ the
same under Windows/MSVC as under Windows/MinGW.

Regards,

Arjen

> -----Original Message-----
> From: Arjen Markus [mailto:Arj...@de...]
> Sent: Saturday, October 19, 2013 4:09 PM
> To: Alan W. Irwi
> Cc: PLplot development list; Andrew Ross
> Subject: Re: [Plplot-devel] Problem builiding the Python bindings on Windows using
> MS VC/C++
>
> Hi Alan,
>
> > -----Original Message-----
> > From: Alan W. Irwin [mailto:ir...@be...]
> > I did install python-2.7.5 and numpy-1.7.1, and immediately
> > encountered the PyArray_FLOAT build errors Arjen encountered.  I
> > created a proper fix for those as of revision 12606.  That allowed me
> > to do a full test of MinGW/MSYS/Wine.  The Python diff summary was the same as
> I got before:
> >
> > python
> >    Missing examples            :
> >    Differing postscript output :  00 03 04 05 06 08 09 11 12 14 14a 15
> > 16 17 18 19 20
> > 21 22 23 25 26 27 29 33
> >    Missing stdout              :
> >    Differing stdout            :  23
> >
> > However, when I looked in detail at those results before and now, they
> > mostly consist of small rounding errors.  The exceptions in the
> > previous test were the major differences for 17, 19, 20, 22, and 25,
> > but for this test example 19 has improved to just a few minor
> > differences. That substantial improvement in example 19 was the result
> > of an actual precision bug fix for the mapform case that occurred as part of revision
> 12606.
> >
> > But I am still completely stumped as to why 32-bit python still has
> > the major differences for the four remaining "bad" examples, and minor
> > differences for many of the rest of the examples when all other
> > languages I have tested on Wine produce perfectly clean results.
> >
> > So the next step in trying to figure out the cause of these problems
> > should be to do some additional platform checks for 32-bit Python.
> > Arjen is moving ahead with those for both the MinGW/MSYS and MSVC
> > Microsoft Windows cases, and I am hoping Andrew will be able to check
> > the 32-bit Python case on Linux.
> >
>
> I have used the MinGW 32-bits platform on Windows to do the same test. I see minor
> differences in the following examples:
> 00 03 04 05 06 08 09 11 12 15 16 17 18 20 21 22 23 25 26 27 29 and 33.
>
> So that list is almost the same as yours, except for example 19 - that is completely
> clean.
>
> I did not run example 14 yet and there is no example x14a.
>
> The examples that show significant differences are: 17 and 25 - the PostScript files
> show extra lines or completely different lines in these two cases.
>
> I also noted that many differences occur with lines like:
>
> 1349 220 M (Python) -- 1350 220 M (C)
> ...  1800 M (Python) -- ... 1799 M (C)
>
> I have not checked what PLplot command is responsible for them, but they occur in
> many examples, so I guess they have to do with the frames.
>
> I will continue with example 14 and then move on to MSVC ...
>
> Regards,
>
> Arjen
>
> DISCLAIMER: This message is intended exclusively for the addressee(s) and may
> contain confidential and privileged information. If you are not the intended recipient
> please notify the sender immediately and destroy this message. Unauthorized use,
> disclosure or copying of this message is strictly prohibited. The foundation 'Stichting
> Deltares', which has its seat at Delft, The Netherlands, Commercial Registration
> Number 41146461, is not liable in any way whatsoever for consequences and/or
> damages resulting from the improper, incomplete and untimely dispatch, receipt
> and/or content of this e-mail.
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the
> latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Plplot-devel mailing list
> Plp...@li...
> https://lists.sourceforge.net/lists/listinfo/plplot-devel
>

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.