Re: [Plplot-general] Obtaining source code related to plplot.h

[Arjen M. <arj...@de...>]

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_...@ve...> 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 <arj...@de...>
>>To: Alan W. Irwin <ir...@be...>; Kouros 
>>Bina <k_...@ve...> 
>>Cc: plplot_general <plp...@li...> 
>>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.