Re: [Plplot-general] Plplot on Mingw

[Walt B. <wal...@gm...>]

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.

It still somehow needs info about the location of some drivers ???

On Thu, Nov 27, 2014 at 1:17 PM, Alan W. Irwin <ir...@be...>
wrote:

> On 2014-11-27 12:20-0700 Walt Brainerd wrote:
>
>  I have again decided to try to build and run Plplot.
>>
>> I am running Windows 8
>>
>> I got it to work fine using Cygwin.
>>
>> I tried many many combinations of Mingw configurations
>> (TDM 32 seems to work, but I want to run 64). Finally, I
>> got one to build and the compile and run a Fortran example.
>>
>> I messed around trying to put the compiler and plplot files
>> in the place I want them permanently, then went back to the
>> test directory and the executable didn't work any more. I get
>> the following: [...]
>>
>
> Hi Walt:
>
> The build tree is a really messy and disorganized place with all sorts
> of stuff there that is relevant to builds but not users needs.
> Therefore, virtually all software packages (including PLplot) are
> organized so that it is possible to copy the user essentials from a
> wide variety of locations in the build tree (chosen with the needs of
> building software in mind rather than the needs of the user) to known
> logical locations (chosen with the needs of the user in mind) in a
> completely separate area called the install tree.
>
> With PLplot (and most other software) you do this essential install
> step by configuring an install prefix with cmake, and once that cmake
> command finishes (preferably starting with an empty build tree) by
> running "make install".
>
> My suggestion is to run "make install" instead of trying to replicate
> most of what it does by hand.  After doing that, please take a look at
> the locations of everything in the install tree; I think you will find
> it quite convenient for your needs.
>
> For example, once PLplot is installed, you should set
> compile options and link options when building _your own code_
> so the compiler finds the PLplot headers in the install tree, and
> the linker finds the PLplot libraries in the install tree.
>
> Afterward, when the run-time loader runs your programme it will need
> to know the location of the PLplot libraries.  On Windows that is
> simply done by putting <prefix>/bin on your PATH (where <prefix> is
> the install prefix you chose when you ran the "cmake" command). That
> should be all you need to do since the PLplot core library alreadys
> knows the installed location of everything else (e.g., driver
> location, map files, fonts, etc.) in the install tree.
>
> In sum, start with "make install", and if the above suggestions do not
> give you sufficient guidance about how to build your own code against
> installed PLplot, then ask more questions here.
>
> 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
> __________________________
>



-- 
Walt Brainerd