Octave for Microsoft Windows: Difference between revisions
Jump to navigation
Jump to search
Add know issue for 4.0.0
(rewrite information 4.0.x install adding octave-forge install and correct 3.8.2 information) |
(Add know issue for 4.0.0) |
||
Line 5: | Line 5: | ||
= Installers for Microsoft Windows = | = Installers for Microsoft Windows = | ||
The easiest way to install GNU Octave on Microsoft Windows is using [http://hg.octave.org/mxe-octave/ MXE] builds. For the current 4.0. | ===Octave-4.0.0 === | ||
The easiest way to install GNU Octave on Microsoft Windows is using [http://hg.octave.org/mxe-octave/ MXE] builds. For the current 4.0.0 release installers can be found [https://ftp.gnu.org/gnu/octave/windows/ here]. | |||
Pre-build octave-forge packages are not prepared from octave-3.8 or later for windows. You can install some octave-forge packages using archived sources and build script. However, small flaws exist in current octave-4.0.0_0 distribution. Before install, correct version number of general and signal packages version to 2.0.0 and 1.3.2, respectively and comment out install io package as "#try_install io-2.2.7.tar.gz" in C:\octave\octave-4.0.0\src\build_packages.m". Then execute | Pre-build octave-forge packages are not prepared from octave-3.8 or later for windows. You can install some octave-forge packages using archived sources and build script. However, small flaws exist in current octave-4.0.0_0 distribution. Before install, correct version number of general and signal packages version to 2.0.0 and 1.3.2, respectively and comment out install io package as "#try_install io-2.2.7.tar.gz" in C:\octave\octave-4.0.0\src\build_packages.m". Then execute | ||
Line 18: | Line 20: | ||
For detailed instruction of installing Octave-Forge packages is shown at [http://wiki.octave.org/Octave-Forge/ Octave-Forge] | For detailed instruction of installing Octave-Forge packages is shown at [http://wiki.octave.org/Octave-Forge/ Octave-Forge] | ||
Known issue | |||
#Both cli and gui cannot handle path name of which contains non-ascii characters. (For 3.8, cli can handle non-ascii code if codepage is properly set to the machine locale) | |||
#Both cli and gui cannot represent non-ascii characters. (For 3.8, cli can handle non-ascii code if codepage is properly set to the machine locale) | |||
See [[Windows_Installer]] for building instructions. | See [[Windows_Installer]] for building instructions. |