216
edits
Windows Installer: Difference between revisions
Jump to navigation
Jump to search
m
→./configure
(→./configure: Octave forge patches in MXE Octave) |
m (→./configure) |
||
| (One intermediate revision by the same user not shown) | |||
| 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. 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. | * <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>--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. | ||