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
__________________________

------------------------------------------------------------------------------
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

Reply via email to