I think I've gotten somewhere, before I had C:\Program Files
(x86)\plplot\bin in my path, but it wasn't until I put C:\Program Files
(x86)\plplot\lib\plplot5.9.4\driversd into the path that I could get to the
point were I could choose how to do the plotting(wingcc, wxwidgets, etc).
But if I choose wxWidgets then I get the error

Failed to load shared library 'comctl32.dll' (error 126: the specified
module could not be found.)

wingcc works fine but I'd like to use wx.

Finally, plplot only works when I run as an administrator, otherwise I get
the debug error I described before, and trying to ignore it only leads to a
fatal error.  I tried to take Stephen's advice but I don't know how, I
passed -DCMAKE_BUILD_TYPE=Release to cmake but I still get plplotd.dll so I
guess it's still a debug build and I still get those debug errors

On Thu, Sep 3, 2009 at 4:24 AM, Ferrell, Stephen <sferrellb...@yahoo.com>wrote:

> Hmmmm...are you building the release version or a debug version?  Sounds
> like you're building the debug version.  Configure for a release build and
> try it again.  I've also found Cmake to be very finicky with Plplot and when
> I get strange results it's sometimes been easier to completely wipe the
> PLplot working files and start all over again.  Also the odd results seem to
> drop off significantly when I limit the number of output devices down to
> just 2 or 3.
>
> ------------------------------
> *From:* Jarl Haggerty <offbeatpatr...@gmail.com>
> *To:* Werner Smekal <sme...@iap.tuwien.ac.at>;
> plplot-general@lists.sourceforge.net
> *Sent:* Wednesday, September 2, 2009 3:36:10 PM
> *Subject:* Re: [Plplot-general] I am trying to get plplot to work in
> visual c++ and I am at my wits end
>
> I tried that, the build process went along a lot more smoothly but now I
> have a problem when I run a program, a window pops up saying debug assertion
> failed
>
>
> File: f:\dd\vctools\crt_bld\self_x86\crt\src\fprintf.c
> Line: 55
>
> Expression: (str != NULL)
>
>
> If I try to debug I get taken to this chunk of code in plcore.c
>
>
>             pldebug ("plInitDispatchTable",
>                      "Opened driver info file %s\n", name);
>             while (fgets (buf, BUFFER2_SIZE, fd) != NULL)
>         {
>                 fprintf (fp_drvdb, "%s", buf);
>         if ( buf [strlen (buf) - 1] != '\n' )
>             fprintf (fp_drvdb, "\n");
>                 npldynamicdevices++;
>         }
>         fclose (fd);
>     }
>     }
>
>
> and the debugger points to the line fprintf (fp_drvdb, "%s", buf);
>
> On Wed, Sep 2, 2009 at 12:54 AM, Werner Smekal <sme...@iap.tuwien.ac.at>wrote:
>
>> Hi,
>>
>> please use the command line which is available if you go to
>> Start->Microsoft Visual ....->Tools. I hope you know what I mean, since I
>> don't know exactly how the programs menu looks like in Vista. Please test if
>> nmake is available (just enter nmake), if not run vcvars32.bat, then nmake
>> should be available. Then configure plplot with
>>
>> cd builddirectory
>> set PATH=builddirectory/dll;%PATH%
>> cmake -G "NMake Makefiles" -DBUILD_TEST=ON path_to_plplot_src
>> nmake
>>
>> examples should be in examples/c and should run.
>>
>> 1) cmake can build Visual C++ projects, but they are not tested and very
>> likely don't work as you found out
>> 2) You need to tell the system where it can find dynamic libraries,
>> therefore you need to add the dll folder to the PATH environment variable
>>
>> Alternatively you can configure plplot for Visual C++ projects like this:
>>
>>  "cmake -G "Visual Studio 9 2008" -DENABLE_DYNDRIVERS=OFF pathtoplplotsrc
>>>
>>
>>
>> This tells cmake to build a shared library but all drivers are linked into
>> the plplot library instead of each driver in its own dynamic library. This
>> might cure your problem (but very likely not).
>>
>> (BTW1: NEVER do the build in source directory. Create a build directory
>> instead and tell cmake where the source is).
>>
>> (BTW2: Instead of running Vista on your laptop you should have installed
>> VirtualBox and installed Vista or XP as a virtual machine. The virtual
>> machine actually runs quite at full speed, but compiling is slower since I/O
>> is not that good in Virtual box.)
>>
>> This email I wrote from my mind, so some things maybe not completely
>> correct.
>>
>> Good Luck,
>> Werner
>>
>>
>> On 02.09.2009, at 09:26, Jarl Haggerty wrote:
>>
>>  Not more than 24 hours ago I had Ubuntu on my laptop and everything was
>>> fine but my work requires the use of a lot of windows programs so I
>>> formatted the hard drive and put Vista on the laptop.  Since then I've been
>>> trying futilely to get plplot to work in Visual Studio 9 2008.
>>>
>>> I extract the plplot source and go to the folder in the visual studio
>>> command prompt and give the command, "cmake . -G "Visual Studio 9 2008""
>>>  That gives me an error saying ifort can't compile a simple test program but
>>> I don't have ifort so I guess that makes sense, if I give the command a
>>> second time it works fine.  Then I open the solutions in Visual Studio, once
>>> again I get a complaint about the fortran component but everything else
>>> seems to work fine.  Now if I build ALL_BUILD all but one of the projects
>>> work fine and visual studio tells me this.
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 1>------ Build started: Project: test_dyndrivers, Configuration: Debug
>>> Win32 ------
>>> 1>Generating test_dyndrivers_dir/hpgl.rc
>>> 1>Could not open driver module hpgl
>>> 1>libltdl error: No error information
>>> 1>Files
>>> "C:/Users/jarl/Desktop/plplot-5.9.4/drivers/test_dyndrivers_dir/hpgl.rc" to
>>> "C:/Users/jarl/Desktop/plplot-5.9.4/drivers/hpgl.rc" are different.
>>> 1>Project : error PRJ0019: A tool returned an error code from "Generating
>>> test_dyndrivers_dir/hpgl.rc"
>>> 1>Build log was saved at
>>> "file://c:\Users\jarl\Desktop\plplot-5.9.4\drivers\test_dyndrivers.dir\Debug\BuildLog.htm"
>>> 1>test_dyndrivers - 1 error(s), 0 warning(s)
>>> ========== Build: 0 succeeded, 1 failed, 33 up-to-date, 0 skipped
>>> ==========
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>> I seem to have all the files I need to make a program with plplot but I I
>>> try that(in visual studio) the program tells me this.
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> *** PLPLOT ERROR, ABORTING OPERATION ***
>>> plInitDispatchTable: Could not open drivers directory, aborting operation
>>>
>>> Plotting Options:
>>>
>>> Enter device number of keyword:
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>> And nothing happens.
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>>> 30-Day
>>> trial. Simplify your report design, integration and deployment - and
>>> focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.
>>> http://p.sf.net/sfu/bobj-july_______________________________________________
>>> Plplot-general mailing list
>>> Plplot-general@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/plplot-general
>>>
>>
>> --
>> Dr. Werner Smekal
>> Institut fuer Allgemeine Physik
>> Technische Universitaet Wien
>> Wiedner Hauptstr 8-10
>> A-1040 Wien
>> Austria
>>
>> email: sme...@iap.tuwien.ac.at
>> web: http://www.iap.tuwien.ac.at/%7Esmekal
>> phone: +43-(0)1-58801-13463 (office), +43-(0)1-58801-13469 (laboratory)
>> fax: +43-(0)1-58801-13499
>>
>>
>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Plplot-general mailing list
Plplot-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-general

Reply via email to