For pipe data on Windows Gnuplot (recent versions > 4.2) - use
wgnuplot_pipes.exe vs. wgnuplot.exe. Even with wgnuplot.exe, using stdin should
work - I believe that is how the Graphics::Gnuplot module functions. However,
both are in the same directory. So if it can find wgnuplot it can find
wgnuplot_pipes. There is also a command line pipe for gnuplot called
pgnuplot.exe. I want to see how this module works but I don't have git set up
on my machine yet - our IT department recently re-imaged my machine blowing
away all my applications and I re-install based on need...
CLIFF SOBCHUK
Core RF Engineering
Phone 613-667-1974 ecn: 8109-71974
mobile 403-819-9233
yahoo: sobchuk
www.ericsson.com
"The author works for Telefonaktiebolaget L M Ericsson ("Ericsson"), who is
solely responsible for this email and its contents. All inquiries regarding
this email should be addressed to Ericsson. The web site for Ericsson is
www.ericsson.com."
This Communication is Confidential. We only send and receive email on the basis
of the terms set out at www.ericsson.com/email_disclaimer
-----Original Message-----
From: Dima Kogan [mailto:[email protected]]
Sent: June-13-11 1:20 PM
To: Chris Marshall
Cc: [email protected]
Subject: Re: [Perldl] PDL::Graphics::Gnuplot
> On Mon, 13 Jun 2011 10:07:47 -0400
> Chris Marshall <[email protected]> wrote:
>
> Hi Dima-
>
> I cloned the repo and and it built out of the box for my cygwin
> install. Pretty impressive watching all the gnuplot window appear
> when running tst.pl! The build and tests passed for win32 ActiveState
> perl but the tst.pl program failed with a bunch of messages like:
>
> 'gnuplot' is not recognized as an internal or external command,
> operable program or batch file.
>
> So somehow the build and tests pass without the module being able to
> run. I suggest adding an INSTALL file with directions on where to
> obtain gnuplot and that it is required for the module to work.
>
> Also, it is very helpful to module users if the module install process
> is "friendly". At the least, the tests should indicate that gnuplot
> was not found and refer the user to where/how to get it.
>
> I had to change the git repository URL to http:// from https:// before
> it would work. Maybe that would make sense for the meta data and your
> github resource.
>
> Looking forward to seeing this on CPAN. If the platform issues can be
> resolved, it could be a strong addition to the PDL development
> environment.
>
Hi Chris.
Unlike plplot and pgplot, Gnuplot is NOT a programming API; rather it's a
standalone interactive application that can also take in input on its STDIN.
Since nothing is being linked, the perl module that talks to gnuplot can be
loaded successfully even if gnuplot isn't installed.
This is why the tests pass (the only test currently implemented is the 'use
PDL::Graphics::Gnuplot' test). Getting better error handling is on my
short-term todo list. I've never touched gnuplot on windows, but I believe at
one point a different executable had to be used in order to pipe data to it.
Does windows even have a concept of "standard input"?
In either case, if this thing is to work on windows, somebody other than me
will have to do the testing and getting it to work there.
Hopefully that isn't a lot of work.
dima
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
