Arjen or Alan: I got the file to compile. I noted it in a separate email to the general list. My file compiles and will execute except, in the console that is in the execution, I get the following error:
 
****** PlPlot error: Aborting operation ****
plInitDispatchTable: could not open drivers directory, aborting operation
 
My file is actually example x11c with the text of the title of the graph altered so that it can be run as a sample to work out all of the compiling and linking issues.
 
In actuality, the renamed example will work if I place it in the following directory:
 
C:\build-plplot\examples\c\Debug\. It executes then -- without the plInitDisaptch etc. error.
 
Also, I tried copying all the executables of the examples in c (x01c.exe through x34c.exe) and placing them in a separate test directory, and I got the same error with the PlInitDispatchTAble: could not open drivers directory, etc. 
 
To be able to operate my eventual compiled files and the executables, I need to be able to install them in an arbitrarily named directory etc.
 
Can someone help me find what to change to get rid of the "plInitDispatchTable: could not open drivers directory" error?
 
Kouros K. Bina

From: Arjen Markus <arjen.markus@deltares.nl>
To: Kouros Bina <k_bina1@verizon.net>
Sent: Tuesday, September 3, 2013 6:52 AM
Subject: Re: [Plplot-general] Obtaining source code related to plplot.h

Hi Kouros,

the actual name of the .lib file is "plplotd.lib" (d for double
precision, that is the default configuration option, at least).

Do you specify the correct path to the library?

Regards,

Arjen

On 2013-09-03 15:49, Kouros Bina wrote:
> Arjen: I was able to modify the CMake file for examples and the
> Makefile.Examples to compile but, I get the following link error.

> 3>ClCompile:
> 2>ClCompile:
> 2> test_plend.c
> 3> xInverarity3Dc.c
> 2>LINK : fatal error LNK1104: cannot open file 'plplot.lib'
> 3>LINK : fatal error LNK1104: cannot open file 'plplot.lib'
> 2>
> 2>Build FAILED.
> 2>
> 2>Time Elapsed 00:00:00.33
> 3>
> 3>Build FAILED.


> Can you suggest a quick path or else something else in the
> Makefile.Examples etc. which goes into creating through the Cmake GUI
> (2.8) and then building ALL_BUILD in MS Visual Studio when opening the
> "VS" Project which the CmAke GUI generates?

> Kouros K. Bina
>
>    *From:* Arjen Markus <arjen.markus@deltares.nl>
>    *To:* Kouros Bina <k_bina1@verizon.net>
>    *Cc:* plpot-general@lists.sourceforge.net
>    *Sent:* Tuesday, September 3, 2013 12:35 AM
>    *Subject:* Re: [Plplot-general] Obtaining source code related to
>    plplot.h
>
>    Hi Kouros,
>
>    you mean you want an example of making just a single program using
>    CMake and the PLplot libraries?
>
>    Hm, I do not have anything ready, perhaps someone else subscribed to
>    the mailing list has. (I do have a small batch file that will do the
>    trick for gcc, but that is not what you are after)
>
>    Regards,
>
>    Arjen
>
>
>    On Mon, 2 Sep 2013 16:53:27 -0700 (PDT)
>    Kouros Bina <k_bina1@verizon.net <mailto:k_bina1@verizon.net>> wrote:
>      > Arjen: Is there a simple example of a CMake or else CmakeLists
>    etc. file which shows how to compile just one file using the CMake
>    GUI and possibly opening up MS VS 2010 and building ALL_BUILD? I was
>    unable to strip the CMAKE file that came with the INSTALL and
>    EXAMPLES in C etc. Kouros K. Bina
>      >
>      >
>      >> ________________________________
>      >> From: Arjen Markus <arjen.markus@deltares.nl
>    <mailto:arjen.markus@deltares.nl>>
>      >> To: Kouros Bina <k_bina1@verizon.net
>    <mailto:k_bina1@verizon.net>> Cc:
>    plplot-general@lists.sourceforge.net
>    <mailto:plplot-general@lists.sourceforge.net> Sent: Monday,
>    September 2, 2013 2:21 AM
>      >> Subject: Re: [Plplot-general] Obtaining source code related to
>    plplot.h
>      >>
>      >> Hello Kouros,
>      >>
>      >> hm, I think the problem is that the PATH environment variable
>    does not include the directory that holds the DLLs. You should find
>    the DLLs in a subdirectory "dll" under the directory holding everything.
>      >>
>      >> The easiest way to test if it all worked is to copy the contents
>    of the "dll" directory into the "Debug" directory holding the
>    executables for the examples.
>      >>
>      >> A more permanent way to do that is to add the full directory to
>    the PATH via the Control Panel/System utility.
>      >>
>      >> (Note: there are more possibilities - I am just illustrating how
>    you can proceed)
>      >>
>      >> Regards,
>      >>
>      >> Arjen
>      >>  On Mon, 2 Sep 2013 02:11:23 -0700 (PDT)
>      >> Kouros Bina <k_bina1@verizon.net <mailto:k_bina1@verizon.net>>
>    wrote:
>      >>> Arjen: I ran the Cmake utility again with Visual Studio 10
>    Win64 generator. I opened the solution (PLPLOT solution -- I
>    believe) and built the "ALL_BUILD". It gave me new directories for
>    each example file that was in C -- such as x10c.dir etc. I had 94
>    succeeded and 0 fail 0 skip. Probably it worked.
>      >>> 
>      >>> There is a debug directory with executables for each test file
>    but the system response is plplotd.dll is missing. How do I get
>    plplotd.dll installed. Kouros K. Bina
>      >>>
>      >>>
>      >>>> ________________________________
>      >>>> From: Arjen Markus <arjen.markus@deltares.nl
>    <mailto:arjen.markus@deltares.nl>>
>      >>>> To: Alan W. Irwin <irwin@beluga.phys.uvic.ca
>    <mailto:irwin@beluga.phys.uvic.ca>>; Kouros Bina
>    <k_bina1@verizon.net <mailto:k_bina1@verizon.net>> Cc:
>    plplot_general <plplot-general@lists.sourceforge.net
>    <mailto:plplot-general@lists.sourceforge.net>> Sent: Monday,
>    September 2, 2013 12:55 AM
>      >>>> Subject: Re: [Plplot-general] Obtaining source code related to
>    plplot.h
>      >>>>  Hi Kouros,
>      >>>>
>      >>>> in addition to what Alan wrote:
>      >>>>
>      >>>> For the MicroSoft compilers (Visual Studio is a convenient GUI
>    around them) you have, basically, two choices:
>      >>>> - Use the suitable Visual Studio generator, apparently
>      >>>>  "Visual Studio 10 Win64"in your case.
>      >>>>  This will build a solution file and associated project files.
>      >>>>  Open the solution in Visual Studio and build the "ALL" project.
>      >>>>
>      >>>> - Use the "NMake Makefiles" generator, this will produce
>    makefiles,
>      >>>>  and then you run the nmake utility which will build all the
>      >>>>  libraries and programs from there on.
>      >>>>  It is the same procedure as Alan described for the other
>      >>>>  platforms.
>      >>>>
>      >>>> (I never use the GUI myself, but I have access to it and should be
>      >>>> able to give some basic advise.)
>      >>>> Regards,
>      >>>>
>      >>>> Arjen
>      >>>> On Sun, 1 Sep 2013 12:49:49 -0700 (PDT)
>      >>>>
>      >>>>> 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?
>      >>>>>
>      >>>>
>      >>>>
>      >>>>
>      >>>> DISCLAIMER: This message is intended exclusively for the
>    addressee(s) and may contain confidential and privileged
>    information. If you are not the intended recipient please notify the
>    sender immediately and destroy this message. Unauthorized use,
>    disclosure or copying of this message is strictly prohibited.
>      >>>> The foundation 'Stichting Deltares', which has its seat at
>    Delft, The Netherlands, Commercial Registration Number 41146461, is
>    not liable in any way whatsoever for consequences and/or damages
>    resulting from the improper, incomplete and untimely dispatch,
>    receipt and/or content of this e-mail.
>      >>>>
>      >>>>
>      >>>>
>      >>>>
>      >>>>
>      >>>>
>      >>>>   
>      >>
>      >>
>      >>
>      >>
>      >> DISCLAIMER: This message is intended exclusively for the
>    addressee(s) and may contain confidential and privileged
>    information. If you are not the intended recipient please notify the
>    sender immediately and destroy this message. Unauthorized use,
>    disclosure or copying of this message is strictly prohibited.
>      >> The foundation 'Stichting Deltares', which has its seat at
>    Delft, The Netherlands, Commercial Registration Number 41146461, is
>    not liable in any way whatsoever for consequences and/or damages
>    resulting from the improper, incomplete and untimely dispatch,
>    receipt and/or content of this e-mail.
>      >>
>      >>
>      >>
>      >>
>      >>
>      >>
>      >> 
>
>
>
>
>    DISCLAIMER: This message is intended exclusively for the
>    addressee(s) and may contain confidential and privileged
>    information. If you are not the intended recipient please notify the
>    sender immediately and destroy this message. Unauthorized use,
>    disclosure or copying of this message is strictly prohibited.
>    The foundation 'Stichting Deltares', which has its seat at Delft,
>    The Netherlands, Commercial Registration Number 41146461, is not
>    liable in any way whatsoever for consequences and/or damages
>    resulting from the improper, incomplete and untimely dispatch,
>    receipt and/or content of this e-mail.
>
>
>
>
>
>



DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited.
The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.