[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: "Official" binary release for Windows
From: |
John D |
Subject: |
RE: "Official" binary release for Windows |
Date: |
Wed, 19 Mar 2014 20:59:06 -0400 |
-----Original Message-----
From: Tatsuro MATSUOKA [mailto:address@hidden
Sent: Wednesday, March 19, 2014 7:34 PM
To: 'John W. Eaton'; John D
Cc: address@hidden
Subject: RE: "Official" binary release for Windows
--- On Thu, 2014/3/20, John D wrote:
> -----Original Message-----
> From: Tatsuro MATSUOKA [mailto:address@hidden
> Sent: Wednesday, March 19, 2014 4:05 PM
> To: John Donoghue; John W. Eaton
> Cc: address@hidden
> Subject: Re: "Official" binary release for Windows
>
> --- On Wed, 2014/3/19, John W. Eaton wrote:
>
> > On 03/07/2014 07:10 PM, John Donoghue wrote:
> > > On 03/07/2014 06:08 PM, address@hidden wrote:
> > >> Message: 3
> > >> Date: Fri, 07 Mar 2014 17:21:01 -0500
> > >> From: "John W. Eaton"<address@hidden>
> > >> To: octave maintainers mailing list<address@hidden>
> > >> Subject: "Official" binary release for Windows
> > >> Message-ID:<address@hidden>
> > >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > >>
> > >> I'd like to start making the Windows installer available from
> > >> ftp.gnu.org. Is it ready for that now? Or are there some
> > >> significant problems that need to be fixed before we should make
> "official" releases?
> > >>
> > >> jwe
> > >
> > > I havent had any issues recently with the build except with gcc.
> > >
> > > I had added a readme html file for the install that may want to be
> > > looked at / modified prior to distribution, depending on what is
> > > distributed or not.
> > >
> > > Would it also make sense to list in it all the packages that are
> > > known to work and compile in windows ?
> >
> > Sure.
> >
> > Is there any good reason that openblas should not be used by default?
> >
> > Are there any significant issues remaining? Is it time to make the
> > 3.8.1 binary available?
> >
>
> I have tested the print feature of gnuplot graphics_toolkit using
> octave-3.8.1 binary for windows downloaded from
> http://octave.osuv.de/3.8/windows/
>
> octave:3> graphics_toolkit gnuplot
> octave:4> fplot (@cos, [0, 2*pi])
> octave:5> print -depsc cos.eps
> warning: print.m: epstool binary is not available.
> Some output formats are not available.
> octave:6> print -dpng cos.png
> octave:3> graphics_toolkit gnuplot
> octave:4> fplot (@cos, [0, 2*pi])
> octave:5> print -depsc cos.eps
> warning: print.m: epstool binary is not available.
> Some output formats are not available.
> octave:6> print -dpng cos.png
>
> Both cos.eps and cos.png have finite file size but do not have graphs.
>
> --
>
> I just tried on my install - It behaves the same as yours when
> switched to gnuplot If I run fltk, print works as expected
I saw octave 'bin' directory and could not find libgd-x.dll (x indicates
version number).
I feel that gnuplot on mxe build is broken and should be corrected.
Otherwise it is better to use gnuplot for windows provided by gnuplot
official site.
Regards
Tatsuro
--
Looking at gnuplot build, its not compiled with gd support so doesnt use it
anyway (at the moment). I have a patch to enable libgd (attached) when
compiling, but it didnt appear to make it magically work with it enabled,
so something else might be missing.
gnuplot-gd.patch
Description: Binary data
Re: "Official" binary release for Windows, John D, 2014/03/08
Re: "Official" binary release for Windows, Tatsuro MATSUOKA, 2014/03/19