Hi Alan
Re the fonts, they appear to be installed, but I don't know if they need some 
sort of map or something, which I couldn't find. I did quite a lot of searching 
but found very little font related help for Cygwin. I guess a lot of people 
only use the command line. Unfortunately I reached a point where I thought I 
was fighting a losing battle.

Re the dll stuff. I can, and often do, run the examples direct from the ide. 
It's not a big deal, now I know how it works. I guess I'm only just finding 
this, because I only usually use static Libs.

Phil

-----Original Message-----
From: "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>
Sent: ‎27/‎10/‎2014 20:42
To: "Phil Rosenberg" <philip_rosenb...@yahoo.com>
Cc: "PLplot development list" <Plplot-devel@lists.sourceforge.net>
Subject: RE: [Plplot-devel] Why is the set_stream() call 
commentedoutforplstream::fill,etc.

On 2014-10-27 18:57-0000 Phil Rosenberg wrote:

> Hi Alan

> Re docbook, I basically ran into a dead end. I couldn't get the
correct fonts install.

Was that simply a package dependency issue?  To repeat what I said
before, the relevant Tex package simply installs symlinks on Linux and
has a dependency on a completely different package which installs the
actual fonts.  So you may find the same situation on Cygwin (but
without the package dependency which would be a package dependency
bug) so that installing a package containing the real fonts followed
by reinstalling the tex font package may be all you need to do.

> I didn't think changing the fonts was really a
sustainable option unless you are interested in changing them
permanently?

I agree the best solution is to get the Cygwin packaging bug fixed for
the exotic fonts.  And the next best would be to find a workaround for
that packaging bug (see above).  But until one or the other of those
is accomplished, trying other fonts locally would be a fine short-term
solution for you just to see the results of any change you make in our
docbook documentation.

> Re the dll issue, I'm not sure that was me as I never use DLLs, but
maybe it was and I lost track of a thread. If it was then sorry for
leaving it hanging. So if it is just a case of setting the path then
that is both easy and a bit frustrating. I have a usr/local/bin
directory in which I store compiled binaries and this is where the
plplot DLLs end up. This folder is in my path all the time and it is
where the examples obviously find the DLLs. Changing this path to run
the examples is a bit of a pain, but now I know this is the situation
I will simply make sure I run the INSTALL project before I try to
debug the examples to make sure I have up to date DLLs.

A much better thing to do (so that you don't mix up build-tree and
install-tree issues and you don't have to constantly be updating your
install) is simply put the build-tree location first on your PATH when
doing build-tree tests, but drop that when doing install-tree tests.
(See scripts/comprehensive_test.sh for how I automatically accomplish
that PATH updating for Windows).

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
__________________________
------------------------------------------------------------------------------
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to