Editing Windows Installer
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 55: | Line 55: | ||
* <code>--enable-devel-tools</code>: Include gdb and an MSYS shell in the binary. | * <code>--enable-devel-tools</code>: Include gdb and an MSYS shell in the binary. | ||
** If you seriously want to work with gdb, you need <code>--disable-strip-dist-files</code> as configure option to keep debug symbols in the installed binaries for debugging on MS Windows. Beware as the total Octave distribution will be > 2 GB, the max. size for an NSIS installer. Your only options are to make 7z-dist, zip-dist or tar-dist installers. | ** If you seriously want to work with gdb, you need <code>--disable-strip-dist-files</code> as configure option to keep debug symbols in the installed binaries for debugging on MS Windows. Beware as the total Octave distribution will be > 2 GB, the max. size for an NSIS installer. Your only options are to make 7z-dist, zip-dist or tar-dist installers. | ||
* <code>--enable-binary-packages</code>: Cross-compile binary modules in [[Octave Forge]] packages. This saves time when installing them once the installation runs on Microsoft Windows | * <code>--enable-binary-packages</code>: Cross-compile binary modules in [[Octave Forge]] packages. This saves time when installing them once the installation runs on Microsoft Windows. | ||
* <code>--with-ccache</code>: The usage of [https://ccache.dev/ ccache] may speed up repetitive compilation drastically. | * <code>--with-ccache</code>: The usage of [https://ccache.dev/ ccache] may speed up repetitive compilation drastically. | ||
* <code>--enable-octave=<octave version></code>: Build a specific version of GNU Octave, which can be one of: | * <code>--enable-octave=<octave version></code>: Build a specific version of GNU Octave, which can be one of: | ||
** <code>release</code> use {{Path|src/release-octave.mk}}, download and build the latest GNU Octave release. | ** <code>release</code> use {{Path|src/release-octave.mk}}, download and build the latest GNU Octave release. | ||
** <code>stable</code> or <code>default</code> uses {{Path|src/stable-octave.mk}} or {{Path|src/default-octave.mk}}, respectively. This builds | ** <code>stable</code> or <code>default</code> uses {{Path|src/stable-octave.mk}} or {{Path|src/default-octave.mk}}, respectively. This builds a self-created distribution tarball from the "stable" or "default" development branch of GNU Octave. See [[#Build installers for Octave development versions|below]] for details. | ||
* <code>--disable-windows-64</code>: Build for 32-bit MS Windows. | * <code>--disable-windows-64</code>: Build for 32-bit MS Windows. | ||
* <code>--enable-fortran-int64</code>: Use 64-bit integers in Fortran code and especially in numerical library code. This option only affects the size of integers used in Fortran code like the BLAS and LAPACK libraries. On 64-bit systems, Octave always uses 64-bit integers for indexing and basic array operations. See [[Enable large arrays: Build octave such that it can use arrays larger than 2Gb.|Enable large arrays]] for details. | * <code>--enable-fortran-int64</code>: Use 64-bit integers in Fortran code and especially in numerical library code. This option only affects the size of integers used in Fortran code like the BLAS and LAPACK libraries. On 64-bit systems, Octave always uses 64-bit integers for indexing and basic array operations. See [[Enable large arrays: Build octave such that it can use arrays larger than 2Gb.|Enable large arrays]] for details. | ||
* <code>--disable-system-opengl</code>: Include software OpenGL libraries. This might help when working with buggy graphics card drivers, but might be slower than hardware accelerated rendering | * <code>--disable-system-opengl</code>: Include a software OpenGL libraries. This might help when working with buggy graphics card drivers, but might be slower than hardware accelerated rendering. | ||
====<code>make</code>==== | ====<code>make</code>==== | ||
Line 111: | Line 110: | ||
==Testing using virtual machines== | ==Testing using virtual machines== | ||
Microsoft provides several virtual machine (e.g. VirtualBox) disk images of MS Windows for | Microsoft provides several virtual machine (e.g. VirtualBox) disk images of MS Windows for 90 days of testing https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/. While primarily meant for testing the MS-Edge browser, the license (given on that page) for these images does not limit the use of these images to just MS-Edge. So it is perfectly possible to also test GNU Octave. | ||
The key idea is to create a shared folder inside the virtual machine to the mxe-octave build directory. It is advised to make it read-only. Either install (or unpack) Octave into MS Windows 10, or create a shortcut to {{Path|octave.vbs}} in the {{Path|<mxe-octave build dir>/dist/octave}} subdirectory on the Linux side. | The key idea is to create a shared folder inside the virtual machine to the mxe-octave build directory. It is advised to make it read-only. Either install (or unpack) Octave into MS Windows 10, or create a shortcut to {{Path|octave.vbs}} in the {{Path|<mxe-octave build dir>/dist/octave}} subdirectory on the Linux side. |