On 2015-05-01 07:45-0000 Arjen Markus wrote:

> Hi Chen,
>
>
>
> I found the receipe to get this working, but it is not entirely trivial - 
> which is a soemwhat nasty and confusing surprise. Here it is:
>
> -        Copy the relevant files into one or more directories that you are 
> going to refer to
>
> -        Use the sequence of commands like this:
>
> set env(PATH) "path-to-dlls;$env(PATH)"
>
> set env(PLPLOT_DRV_DIR) path-to-drvinfo-files
>
> set env(PLPLOT_LIB) path-to-pal-files
>
> lappend auto_path path-to-dlls
>
> package require Pltcl
>
> load plplottcltk.dll Pltcl
>
> ... PLplot is ready
>
>
>
> I tested this with the DLLs in a directory "bin" under the directory where I 
> started tclsh, the driver-info-files in a directory "drivers" and the font 
> and palette files in a directory "data". It is not necessary to separate them 
> like that, but for testing purposes it was easier to do it this way.
>

To Shen-Yeh Chen:

To add to what Arjen said above, my tests of running plplot in a tclsh
environment on MinGW/MSYS show that setting PLPLOT_DRV_DIR and
PLPLOT_LIB is not necessary for my particual version of that platform.
This makes sense because after all, PLplot already knows where
path-to-drvinfo-files and path-to-pal-files are located for both the
build tree and the install tree so there should be no need for you to
remind PLplot of information it alread knows (subject to possible
mistakes about whether you want the build tree or install tree
locations). Note, PLplot uses a heuristic (is current path within the
build tree?) to decide which set of locations it should use. However,
on Arjen's MinGW/MSYS platform (which was a later version than mine)
it turned out that heuristic logic gave the wrong result.  Therefore,
he has long been in the habit of setting those two environment
variables to work around that bug in the heuristic.

The present status is I believe I completely fixed that bug last
week for the git master tip version of PLplot so the heuristic will
work properly for all MinGW/MSYS versions.  Arjen confirmed that fix
worked for a small test on his MinGW/MSYS platform.  So I frankly
don't understand why he needed to set PLPLOT_DRV_DIR and PLPLOT_LIB
above.  Arjen does plan to follow up with comprehensive testing
(without either PLPLOT_DRV_DIR or PLPLOT_LIB set) of that fix as well,
but he hasn't done that yet for a complete final confirmation of that
fix.

Anyhow, if you are using either the build-tree version of PLplot or a
properly installed install-tree version of PLplot for the git master
tip version of PLplot, you will likely not need to set PLPLOT_DRV_DIR
or PLPLOT_LIB now, but if you still do need to set those variables for
the stated conditions and/or Arjen's planned comprehensive testing
shows any problems, I guarantee to get that bug fixed.

By the way, if you are using your own home-built procedure for
installing PLplot (i.e., copying bits and pieces of it from the build
tree to some location), then you likely do have to set PLPLOT_DRV_DIR
or PLPLOT_LIB, but I would highly recommend instead that you simply
use the install target to install PLplot since that is likely more
reliable than any home-built procedure for doing the same task and
also it should allow you (assuming the heuristic now works on all
platforms) to avoid having to set those two environment variables.

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
__________________________

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Plplot-general mailing list
Plplot-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-general

Reply via email to