On 2014-11-27 14:30-0700 Walt Brainerd wrote: > Thanks for your usual very helpful reply. > I guess Canada has a different Thanksgiving Day than the US, > so you are tending to work as usual. > > I did most of what you said. My message was already wordy > so I left out that I did the build with "install" as the prefix. > As you saw from before, I moved all the dll and library files > into one directory with the f90 file for the test--and it worked. > That is a real puzzle. Now it doesn't. Obviously something > must have changed, but I can't figure out what. > > But based on your suggestions, this time I compiled the Fortran > by using -I to find the .mod files and explicitly linked the *.a files > in install/lib. It links fine. Just for completeness, here is the > command I used to compile. > > C:\walt\Software\Plplot\TEST_FT>type compile.bat > gfortran -c -I../BUILD/install/lib/fortran/modules/plplot ft_x00f.f90 > gfortran *.o ../BUILD/install/lib/*.a > > I have both the ...\install and the ...\install\bin directories in > my PATH. I still get > > *** PLPLOT ERROR, ABORTING OPERATION *** > plInitDispatchTable: Could not open drivers directory, aborting operation > > C:\walt\Software\Plplot>echo %PATH% > C:\walt\Software\Plplot\BUILD\install\bin; > C:\walt\Software\Plplot\BUILD\install; > C:\walt\Software\Gfortran\mingw64\bin;C:\Program Files > (x86)\Cmake\bin;C:\Progra . . . > > Is it looking for the "driversd" directory? I think it is where it should be > at ...\install\lib\plplot5.10.0\driversd and contains 6 dlls (I still am not > getting all the drivers I got with Cygwin). I even tried putting the > driversd directory in my path--no deal.
Hi Walt: There are two possibilities I can think of. 1. PLplot does not work very well if there are blanks in path names (such as C:\Program Files above). We have made some progress on such issues in the last year, but I suspect there are a lot more of these issues to be found and fixed so until we get that completely straightened out PLplot users should work around the problem by avoiding all paths with blanks in the name. 2. The "MinGW Makefiles" is not as well tested as the "MSYS Makefiles" generator so you might want to try the latter. Other than those two possibilities, I am pretty much out of ideas. This stuff just works fine on MinGW/MSYS on my Wine version of Windows (with the "MSYS Makefiles" generator and no blanks in any path names), but outside of automatic and extremely comprehensive PLplot testing scripts working fine on that platform (including accessing all installed devices without issues), I have very little other experience with Windows platforms. 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 __________________________ ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general
