On 29 Aug 2010, at 16:13, P Kishor wrote:
> I see several useful modules such as PDL::Graphics::LUT and
> PDL::Transform::Cartography (both of which, surprisingly, do exist in
> my build, in spite of no PGPLOT) use PDL::Graphics::PGPLOT. Why, oh
> why didn't I build PGPLOT? Any cheat sheets out there?
No cheat sheets ... I simply installed pgplot with MacPorts:
sudo port -v install pgplot
(then usually wait a couple of hours while MacPorts pulls a few GiB of unwanted
software :), and it was automatically picked up by the PDL configuration (I'm
building from current source code checked out from the Git repository).
I have never used PGPLOT, though, and trying the demo in the interactive perldl
shell just now, I found to my surprise that it requires the external PGPLOT
package in order to run. After installing this package from source code
(automatic cpan installation doesn't work because the MacPorts include/library
paths have to be specified manually when running Makefile.PL), everything looks
fine.
The only drawback is that MacPorts doesn't offer a universal variant, so PGPLOT
will only be built for the main architecture (i.e. x86_64 on Snow Leopard); not
too much of a problem in most cases.
Question to all: Is the dependency on an external PGPLOT package really
intentional? It's caused by a "use PGPLOT;" in PDL::Graphics::PGPLOT::Window
(and perhaps other modules). If intentional, it should be tested by Makefile.PL
and disable PGPLOT support unless the external package is installed.
Best wishes to everyone,
Stefan
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
