Hi Alan, > > I also had a follow up which crossed with yours. I think we pretty much > agree now > about what is going on, and only differ in that I would suggest doing the > MinGW/MSYS testing first. But doing that after you have completed the MSVC > case > would also work if you prefer that order. >
I do not have a great preference for one or the other - I just had a directory "build-windows-python" on my machine and started working from there :). I do think your suggestion is worthwhile - start with MinGW/MSYS as we have had success there before and then look into the MSVC/C++ case again. After all, the immediate problem was identifying where the differences you detected in WINE are coming from. 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 [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
