Re: Update to Octave 4.0 for Windows

[Nicholas Jankowski]

On Thu, Aug 6, 2015 at 4:54 AM, Tatsuro MATSUOKA <address@hidden> wrote:

----- Original Message -----

> From: PhilipNienhuis 
> To: help-octav
> Cc:
> Date: 2015/8/6, Thu 17:00
> Subject: Re: Update to Octave 4.0 for Windows
>
> Y
> NJank wrote
>>  On Wed, Aug 5, 2015 at 12:36 PM, ijourneaux <
>
>>  ian@

>
>>  > wrote:
>>
>>>  I was wondering if there was a procedure to building updated versions
> of
>>>  Octave 4.0 for Windows? There is a bug fix that Carne implemented wrt
>>>  writing BMP files a couple of weeks ago. The fix required changes to
> the
>>>  Image package and to Octave itself. I think the latest version on the
>>>  website is from May.
>>>
>>>  I can probably get myself setup to build it but didn't want to
> replicate
>>>  the
>>>  effort if there was a system in place to rebuild Octave for Windows
>>>  periodically.
>>>  Ian
>>>
>>>
>>  last I checked there is not a completely Windows-oriented rebuild process.
>>  Unless I'm mistaken, most of the available instructions involve
>>  cross-compiling on Linux for Windows. If fix's just result in modified
>>  m-files, they can just be dropped into the proper place in the Octave
>>  folder tree. Other wise, if it a patch that needs to be worked into other
>>  files, those of us not running linux usually just wait for the generous
>>  souls out there to push a new windows version forward. :D
>>
>>  If you want to either figure out a Windows-only compilation route, or have
>>  a linux platform available to do regular cross compiling, I'm sure no
> one
>>  would complain if the Windows tree included separate stable and
>>  periodically updated development versions. :)
>
> Until some time ago (several months at least) it was possible to build
> Octave natively on Windows using MXE. But it took AGES - while a cross-build
> on Linux took ~ 3 hours, a native build on Windows easily took 24 hours or
> more on the same multiboot box.
>
> AFAIK no one has attempte d native builds lately and it is uncertain if it
> still works.
>
> Philip

AFAIK, JohnD was successful for windows native build with recent mxe-octave.
He used Msys2 (32bit) and its tools and MinGW w62 32 bit compiler (gcc 4.9.2).

Tatsuro 

All I know is when I first started looking about setting things up here to maybe work on a few bugs/patches, etc. I went through an endless recursive loop of link hopping to try to find a set of instructions on what was needed to do so. (only thing obvious was the need for Mercurial to manage the source, but testing many things would be impossible (?) without ability to compile, no?) Eventually I found one page (manual? wiki? I forget) that said in a very roundabout way: "you need Linux". If you get a process together, would be great for that to be captured as a step-by-step on the wiki, whether you manage it all with Windows or do a cross-compile.

Nick J