Windows Installer: Difference between revisions

Jump to navigation Jump to search

Windows Installer (edit)

Revision as of 03:49, 27 August 2019

446 bytes removed ,  27 August 2019
m
Use internal wiki link for MXE.
(→‎Steps to create Windows Installer: Run bootstrap script, make all target before any other target)
m (Use internal wiki link for MXE.)
(One intermediate revision by one other user not shown)
Line 2: Line 2:
GNU Octave is primarily developed on GNU/Linux and other POSIX conformal systems. There have been many efforts in the past to build ports of GNU Octave for Windows. Take a look at the various ports of Octave available for Windows [http://wiki.octave.org/Octave_for_Windows here].
GNU Octave is primarily developed on GNU/Linux and other POSIX conformal systems. There have been many efforts in the past to build ports of GNU Octave for Windows. Take a look at the various ports of Octave available for Windows [http://wiki.octave.org/Octave_for_Windows here].


Recently some work has been done in maintaining a unified build system [http://wiki.octave.org/MXE '''mxe-octave'''] (a fork of [http://mxe.cc/ MXE]) which anyone can use to produce cross as well as native builds of GNU Octave for Windows and Mac OS X platforms. This page contains instructions about creating a Windows installer using mxe-octave.
Recently some work has been done in maintaining a unified build system [[MXE|'''mxe-octave''']] (a fork of [http://mxe.cc/ MXE]) which anyone can use to produce cross as well as native builds of GNU Octave for Windows and Mac OS X platforms. This page contains instructions about creating a Windows installer using mxe-octave.


==Steps to create Windows Installer==
==Steps to create Windows Installer==
Line 90: Line 90:
  hg -v update
  hg -v update
* However, do not keep mxe-octave build dirs for too long. I'd suggest to wipe a build dir after at most two or three months and start over with a fresh clone a la Step 1.
* However, do not keep mxe-octave build dirs for too long. I'd suggest to wipe a build dir after at most two or three months and start over with a fresh clone a la Step 1.
* Sometimes, when using the "--enable-binary-packages" flag, it happens that Octave-Forge packages with binary modules don't work well on the Windows side. Usually the cause is that the Octave dev version has changed too much since the last cross-build of the OF packages. Solution: just do in <mxe-octave>/:
touch src/of*.mk
make <OPTIONS>
mxe-octave will rebuild all OF packages then incl. the offending binary modules.
* In the mean time, regularly clean up <mxe-octave build>/log to save disk space. After a first successful build there's no more use for the log subdirs for each package, so you can wipe them all.
* In the mean time, regularly clean up <mxe-octave build>/log to save disk space. After a first successful build there's no more use for the log subdirs for each package, so you can wipe them all.


Retrieved from "https://wiki.octave.org/Special:MobileDiff/11745...12248"

Navigation menu