I think it is important to keep this exchange on the plplot-general
list so that is what I have done. More below.
On 2013-09-01 03:55-0700 Kouros Bina wrote:
> Alan: I used CMake 2.8 GUI and, I added BUILD_TEST is on and jpeg.
What does one do after running CMake 2.8 GUI? Also, I determined that
my compiler is Visual Studio 10 Win64. I cannot determine what the
next step is. I would like to try some of the examples and then make
some programs for plotting contour plots from data stored in files.
What is done after running CMake 2.8 GUI?
The general answer to your question is you run the targets that have
been configured by our CMake-based build systems. Those include "all"
(to build everything needed for an install) and "install" to install
just the essential elements of PLplot that have been built in the
build tree to the install tree (but do not install intermediate files
that are not used in the final product to make the install tree as
compact as possible). Also, for all Unix platforms and some Windows
platforms the targets "test_noninteractive" and "test_interactive" are
available to test all non-interactive and interactive devices using
all our standard PLplot examples in the build tree. Note on Windows
those targets are only available if you have MSYS on your PATH since
those targets depend on MSYS applications such as bash.exe.
Note that although my principal platform is Linux, I also do some
command-line testing using the combination of
MinGW-4.7.2/MSYS/Wine-1.6. For that combination I use either the
"MSYS Makefiles" or "MinGW Makefiles" CMake generator and both work
well on the Wine-1.6 version of Windows. I am also assured by others
that those two generators give good results for the Microsoft version
of Windows as well.
For the "MSYS Makefiles" case, I build the targets referred to above
For the "MinGW Makefiles" case, I remove sh.exe from the PATH
but leave the rest of MSYS on the PATH including
bash.exe. Then after
cmake -G "MinGW Makefiles" ....
is run I build the above targets using
etc. The reason why sh.exe must be removed from the PATH is the
mingw32-make.exe application changes its interpretation of paths in a
way that is not consistent with what CMake has configured if sh.exe is
on the PATH.
I hope these generalities (which I am forced to use since I don't have
access to the compilers you use) will help make what is said in the
wiki a bit clearer. However, if you have further questions specific
to your particular set of Microsoft compilers, I think there are
others lurking here who have enough experience with those to give you
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).