On 2011-06-06 12:42+0100 Richard Jackson wrote: > Hi Alan, > > I thought I would have a go at building the examples as per your > instructions below, but I'm confused as to exactly what you mean by the > cmake instructions.
I assume you meant make (as opposed to cmake) instructions. Below, I will try to make those clearer. > Anyway, I started with a new build directory and ran > cmake -G "MinGW Makefiles" -DBUILD_TEST=ON -DCMAKE_INSTALL_PREFIX= .. > It ran through and compiled all the C examples but failed on the C++ ones as > usleep() was undefined. I copied the compiled C examples and then reran the > make without the -DBUILD_TEST=ON and installed plplot OK. > Then I tried running the examples. They all list all 18 drivers but will not > load any of them. You are obviously aware of this already, but just to clarify for others, cmake does not build anything. Instead, it prepares your choice of backend tool to do the actual build. That tool choice is done with the cmake back-end generator chosen with the cmake -G option. For example, -G "MinGW Makefiles" uses a generator that prepares Makefiles for the MinGW version of make and MinGW compilers. That generator only works if sh.exe from MSYS is not on the PATH. (You can arrange that by removing/renaming sh.exe or by removing MSYS from your PATH altogether.) In contrast, -G "MSYS Makefiles" chooses a generator that prepares a very different set of Makefiles for the MSYS version of make with both MinGW (for the compilers) and MSYS on the PATH. I have read your further posts today, and it appears you have finally had success with Qt-4.7.3 for a special version of the latest MinGW compiler, but so far your testing of the result has been limited to running a few of the examples by hand using the results from the "MinGW Makefiles" generator. For the next step I suggest you install MSYS on your platform (if that is not available already) and try using the "MSYS Makefiles" cmake generator. That is the generator I have had succes with on wine. Because MSYS will be on your PATH, that automatically makes bash.exe from MSYS available. (Another possibility for bash.exe is the winbash package. We have used that in the past for Windows tests, but it is a very old and limited version of bash which is no longer maintained and which does not work for all components of our testing system because of that limited functionality. Therefore, I can no longer recommend winbash unless there is some strong reason why you do not want to install MSYS on your windows platform.) bash.exe is a prerequisite for our test system and should make it possible for you to run the test_noninteractive and test_interactive make targets as recommended below. (Note, these targets will not be available unless bash.exe is on your PATH so that may have been the source of your previous difficulty with these tests.) These targets run _all_ noninteractive and interactive examples in the build tree for a fairly comprehensive run-time check of every component of PLplot that you are able to build. Warning. The plot files that result from running the test_noninteractive target will consume something like 2GB of disk space (until you remove your build tree where the tests are done). Good luck with your further testing of your PLplot build on Windows with a modern Qt. Alan > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > Sent: 04 June 2011 20:26 > In the past here is how I have tested PLplot under wine. > > Put the dll subdirectory of the top-level build directory (where all > the build-tree dll's are automatically collected for the Windows > platform case) on your PATH, put MSYS _last_ on your PATH, use the > "MSYS Makefiles" cmake generator, and use the -DBUILD_TEST=ON option > for cmake. Our test system requires a modern bash which is > why I suggested putting MSYS (which supplies a modern bash for > windows) on your PATH. The "MSYS Makefiles" cmake generator enables > cmake to generate make files that also depend on the msys version of > bash as well as other msys applications. > > Then run > > make VERBOSE=1 test_noninteractive >& make_test_noninteractive.out > make VERBOSE=1 test_interactive >& make_test_interactive.out > > The former tests essentially all non-interactive devices (including the > qt ones). The latter will display lots of interactive results on your > desktop > (including the qt ones). > > For the test_interactive target, we are most interested in any errors > showing up in make_test_interactive.out so our test systems uses the > -np PLplot option to remove the pause between pages for most examples > so you don't have to interact with them. However, that option does > not yet work for all test examples so you might have to do some > clicking (and sometimes just hitting the enter key) to get through a > subset of the interactive examples. > > There is one caveat to the above for the present case. I am a bit > concerned about how a modern MSYS will interact with the older MinGW > versions you tend to get with Qt. However, I used objdump -p (I don't > have access to the Cygwin version of ldd yet) to show that bash.exe > supplied by MSYS has no MinGW dll dependencies. So I think the above > MSYS-dependent steps will work for you even when you are using a Qt > version of MinGW. > > Assuming the above tests work well, then the VERBOSE option tells you > all the compile and link options that you need to get any application > to work with PLplot. > __________________________ 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
