1,847
edits
Windows Installer: Difference between revisions
Jump to navigation
Jump to search
→Testing using virtual machines: Add URL to more general VM test disc image
(Add categories, ensure MS Windows.) |
(→Testing using virtual machines: Add URL to more general VM test disc image) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 31: | Line 31: | ||
--enable-binary-packages \ | --enable-binary-packages \ | ||
--with-ccache \ | --with-ccache \ | ||
--enable-octave=<octave version> | --enable-octave=<octave version> | ||
</pre> | </pre> | ||
| <pre style="min-width:330px;"> | | <pre style="min-width:330px;"> | ||
| Line 41: | Line 39: | ||
--with-ccache \ | --with-ccache \ | ||
--enable-octave=<octave version> \ | --enable-octave=<octave version> \ | ||
--enable-fortran-int64 | --enable-fortran-int64 | ||
</pre> | </pre> | ||
| Line 59: | 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. Furthermore, some packages require patches to cross-compile successfully (or with current Octave versions). Those additional patches would be missing when compiling the original packages from Octave Forge on Windows later on. Some Octave Forge packages require a working Octave during compilation. Therefore, the correct version(!) of Octave must be installed on the host system. | ||
* <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 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>stable</code> or <code>default</code> uses {{Path|src/stable-octave.mk}} or {{Path|src/default-octave.mk}}, respectively. This builds from 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>-- | * <code>--disable-windows-64</code>: Build for 32-bit MS Windows. | ||
* <code>--enable- | * <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>-- | * <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>--with-pkg-dir=../mxe-octave-pkg</code>: If you are working with several build trees, you can share a common package directory. | |||
====<code>make</code>==== | ====<code>make</code>==== | ||
| Line 114: | Line 111: | ||
==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 about one month of testing | ||
* https://developer.microsoft.com/en-us/windows/downloads/virtual-machines | |||
* https://developer.microsoft.com/en-us/microsoft-edge/tools/vms (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. 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. | ||