Re: MXE-octave changes

[Rik]

On 01/16/2014 11:25 PM, address@hidden wrote:
> Message: 5
> Date: Thu, 16 Jan 2014 18:16:33 -0500
> From: "John W. Eaton" <address@hidden>
> To: octave maintainers mailing list <address@hidden>
> Subject: mxe-octave change
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I moved the functionality of the mk-dist script in the mxe-octave
> build system into the Makefile and removed the mk-dist script.
>
> Now you just need to run
>
>     make nsis-installer
>
> or
>
>     make tar-dist
>
> to build everything and generate an installer or tar file containing
> all the files.

Maybe update the wiki as well (http://wiki.octave.org/Windows_Installer)?
> Currently this will build the stable-octave target.  If you have a
> previous build that used the octave target, then I think you'll end up
> with both versions included in the tar file or installer so some care
> is needed to avoid having unintended files in the binary distribution.
> Eventually I hope we can eliminate that problem so that the files that
> are included are predictable without having to run "make clean" first
> before building the installer (and everything else).

I'm using the unintended consequences to good effect right now.  I build
the development version of Octave which gets installed in the MXE tree as
octave-4.1.0+.exe.  When I run one of the dist targets the dev version gets
packaged as well.  It would be nice to not install so much cruft, but
hopefully there will be changes to the build system which also make it easy
to select which version to compile and install.

--Rik