RE: Re: Re: Contributing to Windows (MXE) and Linux versions: cannot, find the sources on MXE

[JohnD]

> -----Original Message-----
> From: address@hidden [mailto:address@hidden
> Sent: Saturday, June 20, 2015 7:08 PM
> To: address@hidden; address@hidden;
> address@hidden
> Subject: Re: Re: Re: Contributing to Windows (MXE) and Linux versions: cannot,
> find the sources on MXE
> 
> --- john.david.donoghue
> > On 06/20/2015 01:36 PM, address@hidden wrote:
> > > Message: 2
> > > Date: Sat, 20 Jun 2015 13:23:51 -0300
> > > From: Rafael Monteiro<>
> > > To: Jordi Guti?rrez Hermoso
> > > Cc: Octave Maintainers
> > > Subject: Re: Contributing to Windows (MXE) and Linux versions: cannot
> > >   find the        sources on MXE
> > > Message-ID:
> > >
> > > <CAKvq7-uoM-_D5jDOEjs5xGrCTukkZqSqPtXfc=cX-
> address@hidden>
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > Thanks, Jordi.
> > >
> > > That makes sense, but I thought it would keep the downloaded files
> > > somewhere. Is there any way I can tell it to "keep the sources", so
> > > I can change them and run make to see the effects on a Windows build? Or
> else:
> > > can I tell MXE-Octave to get the sources from my local ~/octave folder?
> > > Perhaps I could setup a Mercurial server and tell MXE-Octave to look
> > > at my local repository. Does that make sense? Is there a simpler approach?
> > >
> > > I'm curious to know how Octave Windows developers do it.
> > >
> > > Regards,
> > >
> > > Rafael Monteiro
> >
> > It does save the download sources in the pkg folder when creating building 
> > the
> subpackages, however none of them are distributed in the installer.
> >
> > I have been able to then compile octave from sources natively in windows
> after installing a cross build installer using the --enable-devel-tools 
> option in
> mxe-octave, however it is _far_ faster to make changes as a patch in mxe-
> octave and regenerate the mxe-octave installer than it is to recompile octave
> natively in windows.
> >
> I am glad to here that your success using --enable-devel-tools. What does mean
> "after installing a cross build installer"?
> 
> I think that you are now using msys2 + 32 bit gcc compiler of MinGW64 but not
> toolchain from MinGW original site.
> If you are using the tool that I guess, it would be grateful to update the 
> wiki
> page:
> http://wiki.octave.org/Windows_Install
> 
> Tatsuro


Still a work in progress, however it does allow compile of octave within 
windows using all the other packages already compiled. It is using the gcc etc 
cross compiled within mxe--octave.
I did have to patch octave with octave-1-fixes.patch from mxe-octave in order 
to compile.

There are also a few additional packages that should probably be added with the 
devel option in order to be complete - octave will warn about them not being 
present, but using the release tarball, they are not needed.

I have also succeded In getting mxe-octave to compile in msys3 (32 bit) and 
pushed changes to mxe-octave to support this.

I believe I also have octave under msys2 64 bit almost complete - (or almost) - 
I compiling stable-octave as I type, however a few more  changes are needed to 
be pushed up in order for it to work.