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.
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.

I tried again adding C:\msys\1.0\bin to my PATH and running
  cmake -G "MSYS Makefiles" -DBUILD_TEST=ON -DCMAKE_INSTALL_PREFIX= ..
but it fails in the same way.

I'll have a look at Arjen's DLL dump tonight, but at first sight it looks
like he has a different gcc compiler, its showing d:\gcc4.6\bin\ in his
PATH. gcc -v reports version 3.4.5 on my system for the MinGW included with
Qt 4.5.3 and its reporting  version 4.5.2 for the latest MinGW download. The
MSYS gcc version is also 4.5.2.

Regards
Richard

-----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.


------------------------------------------------------------------------------
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

Reply via email to