On Mon, 16 Oct 2006, Sisyphus wrote:

> 
>  ----- Original Message -----
>  From: "Randy Kobes" <randy@[...].ca>
> 
> > I'd have to add the necessary stuff to satisfy 1) or 2)
> > above, but I'd be happy to host the binary you built with
> > the added features - just let me know when, and where.
> >
> 
>  Thanks - when 2.4.4 comes out, I'll take you up on that offer.
> 
>  There's a couple of "untidy" aspects about my PDL binary that should be
>  addressed first, however:
> 
>  Firstly, the PDL::IO::GD component of PDL is built against a dynamic gd
>  library - which itself needs to find the jpeg and zlib (and perhaps also png
>  .. not sure) dll's. So my current PDL binary therefore needs to have the gd,
>  jpeg, and zlib dll's included with it. Do you happen to know of a *static*
>  gd library I could build PDL against, thus eliminating the need to
>  distribute those dll's ? (Can be either an MSVC-built or MinGW-built static
>  library.) I guess I might be able to build such a static library myself, if
>  need be .... I haven't actually tried.

I have one, built with VC++, which includes jpeg, zlib, and
png support - I'll send a copy to you privately. You'll have
to arrange to define NONDLL when compiling something against 
this lib, as the default is to use a dll.

>  The PDL::PGPLOT component of PDL requires that the PGPLOT module be
>  installed - so it would be nice to put a PGPLOT ppm on uwinnipeg, too. There
>  again, my PGPLOT distro is built against a dynamic pgplot library, and needs
>  to be packaged with pgplot.dll, cpgplot.dll and the png.dll. I'll try to
>  build a static pgplot library, but if I can't, then we'd be stuck with
>  distributing those dll's. Is that an issue with a ppm distro ?

A static lib would be easiest, but if not possible, or if 
there's other packages that would use the dll and thus
the size savings would be an advantage, it's possible
to install a dll (or several of them) through a post-install
script; see
    http://theoryx5.uwinnipeg.ca/ppms/XML-LibXML-Common.ppd
for an example; the scripts and dlls themselves are in
    http://theoryx5.uwinnipeg.ca/ppms/scripts/

>  Included, too, is a fonts file (grfont.dat) which is a necessary part of the
>  PGPLOT distro. It can be installed anywhere.

That could also be done with a post-install script.

>  There's also a graphics window (grwnd.exe) that can be used to view PGPLOT
>  output - it would be nice if that could be included in the ppm distro. (It
>  just needs to be installed anywhere in the path.)

If you can arrange to put that in the blib/script/
subdirectory after building, then the ppm package
should install it in the C:\Perl\bin directory (with
the ActivePerl 819, they'll go under C:\Perl\site\bin,
which might require a PATH addition).

>  And there's a couple of environment variables that need to be set before the
>  PGPLOT module can effectively be used - I guess we can make the user aware
>  of this at the 'ppm install' stage ?

Yes, a post-install script can print something out at
the end. You might also include a warning, or fatal
error, as appropriate, when using the module if these
environment variables aren't set, as there's probably
a non-zero chance a user would miss such a post-install
message.

>  Other than that, it should all be fairly straight forward - an ExtUtils::F77
>  ppm package (not really needed for anything other than satisfying
>  "dependency" requirements), and a PDL::NetCDF ppm package which has been
>  built against a static netcdf library.
> 
>  In all, I'd be looking at providing just the four ppm packages - PDL,
>  PGPLOT, EU::F77, and PDL::NetCDF. My current binary package (which includes
>  those 4 ppm packages, plus the dll's etc.) is 5.7 megs - just to give you
>  some idea of the space that would be consumed.

That's no problem for us.

-- 
best regards,
Randy

_______________________________________________
PPM mailing list
PPM@[...].com
http://listserv.ActiveState.com/mailman/listinfo/ppm