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.
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.
On Wednesday, 18 December 2013, 17:06, Alan W. Irwin
<[email protected]> wrote:
To Andrew, Jerry, Arjen, and Phil:
There are some important questions below for you. I need those
questions answered for the release notes (README.release) for the
forthcoming release.
For example, when I am done with my testing, my test summary
in README.release will read
Comprehensive tests for a complete system build environment were run
on 64-bit Debian Wheezy Linux on AMD-64 hardware.
Comprehensive tests for a limited (qt, cairo, and wxwidgets PLplot
components were dropped) epa_build environment were run on 64-bit
Debian Wheezy Linux on AMD-64 hardware.
Comprehensive tests for a complete epa_build environment were run
on 64-bit Debian Wheezy Linux on AMD-64 hardware.
Comprehensive tests for a limited (qt, cairo, and wxwidgets PLplot
components were dropped) epa_build environment were run for 32-bit
MinGW/MSYS/Wine on AMD-64 hardware.
I need similar tests summaries from all of you that have run tests for
this release. I give preliminary (and quite uncertain, see all the
question marks) versions below. Please send back the corrected
versions of these test summaries. In most cases the question marks
should be quite easy to replace with your actual test data. However,
the phrase "Limited tests??" is a bit of a special case. It should be
replaced by one of "Comprehensive tests" (if you actually ran the
scripts/comprehensive_test.sh script), a phrase summarizing the exact
test you ran such as "ctest + the test_noninteractive target in the
build tree" for intermediate testing, or "Limited tests" for those
cases where you actually only did a few tests by hand.
@Andrew:
Limited tests?? for a complete system build environment were run
on 64-bit?? Debian unstable on AMD-64 hardware??
Limited tests?? for a complete system build environment were run
on 64-bit Ubuntu version?? on AMD-64 hardware?
@Jerry:
The Ada subset of the ctest tests were run in the build tree for a
limited (what PLplot components were dropped??) build environment on Mac OS X
(version??) on AMD-64 hardware??
@Arjen:
Limited tests?? for a complete system build environment were
run for 64-bit?? Cygwin on Windows (version ??) for AMD-64 hardware??
Limited tests?? for a limited (what PLplot components were dropped??)
system build environment were run
for 64-bit?? MinGW/MSYS on Windows (version ??) on AMD-64 hardware??
Limited tests?? for a limited (what PLplot components were dropped??)
system build environment were run for 64-bit?? MSVC (version??) +
Ifort (version??) compilers on 64-bit Windows (version ??) for AMD-64
hardware?? The "NMake Makefiles" generator yielded good results while
the "Visual Studio 10" generator appropriate to the VS2010 IDE did not
work indicating there are some CMake bugs for that generator that need
to be addressed.
@Phil:
Limited tests?? for a limited (what PLplot components were dropped??)
system build environment were run for both 32-bit and 64-bit MSVC
(version??) compilers on 64-bit Windows (version ??) for AMD-64
hardware?? The "NMake Makefiles" generator yielded good results while
the "Visual Studio 11" generator appropriate to the VS2012 IDE had
some issues that could be worked around but which nevertheless
indicated there are some CMake bugs for that generator that need to be
addressed. The 3.0 version of wxwidgets was tried for these tests but
required some CMake patches <available at
http://www.cmake.org/Bug/view.php?id=14587and
http://www.cmake.org/Bug/view.php?id=14642> to work.
Thanks in advance for your assistance with editing these test summaries.
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
