Hi Phil: Thanks for that paragraph. There are two questions at the end of this concerning the interpretation of that paragraph.
On 2013-12-18 12:31-0800 phil rosenberg wrote: > Hi Alan > I've never tried the actual test scripts - there was a note on the wiki that said they don't work on Windows and I always assumed they were shell scripts so I wouldn't be able to run them. Yes, they are essentially bash shell scripts which work fine for both Unix and also the MinGW/MSYS case. So theoretically if you installed MSYS and put it (but not MinGW) on your PATH you should be able to do complete run-time testing of PLplot for the MSVC/nmake case. In practice, however, Arjen tried that last year, and ran into difficulties which he has not been able to figure out so far. If you would like to try this yourself some time after this release, then MSYS is easy to download and install. Just follow the directions at http://sourceforge.net/projects/mingw/files/Installer/mingw-get/ (Note for the Wine case I used an earlier version of the installer they made available last year there, and I haven't tried the recent version they have now.) Typically you obtain a complete install of MinGW + MSYS in about 5 minutes, and the MinGW part of that can be ignored by not putting MinGW on your PATH. > > Anyway, I've noted below what I have actually done, which is really to test > that the libraries build and a small amount of use in anger as it were. > However, now I have these built with wxWidgets 3.0 I can confirm the bug that > Joost described a short while ago with the examples - it looks like only the > original window area is ever redrawn. However my own code works fine. Looking > at that will have to wait until the new year now I imagine. > > Anyway modified paragraph below. Feel free to modify further to match the > style of the rest of the document. > > Successful builds were achieved using Visual Studio 2012 on 64 bit Windows 8 with wxWidgets 3.0 (x86 and x64 builds) and Visual Studio 2008 on 32 bit Windows 7 with wxWidgets 2.8 (x86 builds only). In both cases only the C and C++ bindings were built. The "NMake Makefiles" generator with Visual Studio 2012 was also successfully used to build the same configurations. When using wxWidgets 3.0 CMake patches were required and these are available at http://www.cmake.org/Bug/view.php?id=14587 and http://www.cmake.org/Bug/view.php?id=14642. Some problems also exist with the use of Plplot's wxWidgetsApp with wxWidgets 3.0 which were observed in the examples, however plots embedded in wxWidgets apps seem to work fine. With the above patches applied the "NMake Makefiles" generator gave results which built without problems. The "Visual Studio 9 2008" generator with wxWidgets 2.8 also gave results which built without problems. The "Visual Studio 11" and "Visual Studio 11 Win64" generators had some issues which could be worked around but which nevertheless indicated there are some CMake bugs for that generator that need to be addressed. To help me interpret what you said, here is my understanding of the background (please correct if I have this wrong): The CMake documentation has the following table concerning visual studio generator names and what they actually do: Visual Studio 6 = Generates Visual Studio 6 project files. Visual Studio 7 = Generates Visual Studio .NET 2002 project files. Visual Studio 10 = Generates Visual Studio 10 (2010) project files. Visual Studio 11 = Generates Visual Studio 11 (2012) project files. Visual Studio 12 = Generates Visual Studio 12 (2013) project files. Visual Studio 7 .NET 2003 = Generates Visual Studio .NET 2003 project files. Visual Studio 8 2005 = Generates Visual Studio 8 2005 project files. Visual Studio 9 2008 = Generates Visual Studio 9 2008 project files. Furthermore, http://en.wikipedia.org/wiki/Visual_studio says that the Windows Visual Studio IDE includes MSVC (presumably the latest version of that when the IDE version gets released). And now for two questions concerning the interpretation of your paragraph: Does the above background information combined with what you said in your paragraph mean that you used a consistent Visual Studio 12 (2013) IDE (and corresponding MSVC compiler) for all your tests, but for different Visual Studio generators that you mentioned? If so, this implies the Visual Studio 12 (2013) IDE can accept project files written by CMake generators for earlier Visual Studio versions. And for the nmake test can you confirm you used the MSVC compiler associated with the Visual Studio 12 (2013) IDE, but not the IDE itself? (I assume you did not use the IDE since nmake is a command-line tool.) Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
