Octave for Microsoft Windows: Difference between revisions

Jump to navigation Jump to search
→‎Octave-{{Release}}: added --force-gui note.
(gnuplot)
(→‎Octave-{{Release}}: added --force-gui note.)
(22 intermediate revisions by 5 users not shown)
Line 1: Line 1:
:''This article is about using pre-built installers of Octave for Windows; for instructions about building it, see [[Windows Installer]].''
:''This article is about using pre-built installers of Octave for Windows; for instructions about building it, see [[Windows Installer]].''


GNU Octave is primarily developed on GNU/Linux and other [https://en.wikipedia.org/wiki/POSIX POSIX] conform systems. The ports of GNU Octave to Microsoft Windows use different approaches to get most of the original Octave and adapt it to Microsoft Windows idiosyncrasies (e.g. dynamic libraries, file paths, permissions, environment variables, GUI system, etc). Bear this in mind and don't panic if you get unexpected results. There are a lot of suggestions on the mailing lists for tuning your Octave installation. GNU Octave standalone ports for Windows are independently compiled using either the [http://mingw.org MinGW] or Microsoft Visual Studio development environments (3.6 or before).
Windows installers are available for the latest version of Octave (Octave {{Release}}, released on {{Release Date}}) from [https://ftp.gnu.org/gnu/octave/windows/ ftp.gnu.org/gnu/octave/windows/]. Users are encouraged to use the latest version unless a specific feature or requirement warrants using an older version of the software. Version specific instructions and installation notes are provided below.
 
Be advised that GNU Octave is primarily developed on GNU/Linux and other [https://en.wikipedia.org/wiki/POSIX POSIX] conform systems. The ports of GNU Octave to Microsoft Windows use different approaches to get most of the original Octave and adapt it to Microsoft Windows idiosyncrasies (e.g. dynamic libraries, file paths, permissions, environment variables, GUI system, etc). Bear this in mind and don't panic if you get unexpected results. There are a lot of suggestions on the mailing lists for tuning your Octave installation. GNU Octave standalone ports for Windows are independently compiled using either the [http://mingw.org MinGW] or Microsoft Visual Studio development environments (3.6 or before).


__TOC__
__TOC__
Line 7: Line 9:
= Installers for Microsoft Windows =
= Installers for Microsoft Windows =


===Octave-4.0.2===
===Octave-{{Release}}===
The easiest way to install GNU Octave on Microsoft Windows is by using [http://hg.octave.org/mxe-octave/ MXE] builds. For the current release, both 32-bit and 64-bit installers and zip archived packages (.zip and .7z formats) can be found at [https://ftp.gnu.org/gnu/octave/windows/ ftp.gnu.org/gnu/octave/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. release installers and zip archived packages can be found at [https://ftp.gnu.org/gnu/octave/windows/ ftp.gnu.org/gnu/octave/windows/]. Unofficial 64 bit binary is available at [http://www.tatsuromatsuoka.com/octave/Eng/Win/ File list of Octave for Windows]
For executable installers, the user can simply run the downloaded file and follow the on-screen installation prompts.  It is recommended that the installation path does not include spaces or non-ASCII characters. Shortcuts to the program will be created automatically.


Known issue specific to windows version 4.0
For the zip archives, the user should extract the file content to a directory on the harddrive (such as C:\Octave). Manual shortcuts can then be created to either the octave.bat or octave.vbs files in the main installation directory. '''Note that starting with Octave 4.4.0, the shortcuts will no longer start the graphical user interface by default.  The user needs to add --force-gui to any manual shortcuts to start Octave with the GUI. (Right-click on the shortcut, select Properties, and add --force-gui to the end of the Target field.)'''
#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)
 
Known issues specific to 64 bit binary.
#nan package cannot be installed by "pkg install" commands. Workaround is to execute "setenv CC gcc" before "pkg install".


====Packages====
====Packages====
Pre-built octave-forge packages are prepared for official release. If you installed Octave 4.0.1 using the executable installer you can confirm the package list by typing the command below from the Octave command prompt:
A selection of pre-built, octave-forge packages are prepared for all versions of the official release. If you installed Octave using the executable installer, you can confirm the package list by typing the command below at the Octave command prompt:


   >> pkg list
   >> pkg list


If you instead installed Octave from the .zip archive, you need to first rebuild the package list on your local machine. (The command above will produce a blank output.) Do this by typing the following command:
If instead you installed Octave from the .zip archive, you need first to rebuild the package list on your local machine. (The command above will produce a blank output and packages will be inaccessible before rebuilding.) Do this by typing the following command:


  >> pkg rebuild
  >> pkg rebuild


Packages can be updated by running
 
  >> pkg update


Other packages can be installed by
Other packages can be installed by running


   >> pkg install -forge <package name>
   >> pkg install -forge <package name>


For detailed instruction of installing Octave-Forge packages is shown at [http://wiki.octave.org/Octave-Forge Octave-Forge]
To install a new or updated package version manually, the package file can be downloaded from the [https://octave.sourceforge.io/packages.php Octave-Forge website]to the working directory and can be installed using:
 
For 64 bit binary distributed from the unofficial site, pre-built package are not prepared.
Please follow the instruction on the distribution page.
 
===gnuoplot===
Current octave for windows ships not full featured gnuplot. Therefore you cannot use pull gnuplot graphics toolkit features
(e.g. cannot use cairo based devise like "-dpdfcairo"). If you want use full features of gnuplot_graphics toolkit,
please use the following instruction
 
# Download and install gnuplot if you do not have it. You can find the windows installer in the [https://sourceforge.net/projects/gnuplot/files/gnuplot/ gnuplot web site for Files section] The latest version is 5.0.3.


# Make .octaverc in your USERPROFILE directory. We can find path of USERPROFILE directory by
  >> pkg install package_file_name.tar.gz


  >> getenv USERPROFILE
Detailed instructions for installing Octave-Forge packages are given at [http://wiki.octave.org/Octave-Forge Octave-Forge]


make .octaverc by your favorite text editor and set gnuplot_binary e.g.


gnuplot_binary 'C:\Program Files (x86)\gnuplot\bin\gnuplot,exe'
''Note that a security related issue in Windows XP currently prevents Octave from retrieving packages from the website automatically for installation or updates when running under that Operating System, and manual package installation is necessary to update or install new packages.''


Please do not forget to quote the path name by single quote (') if name of which has (a) white space(s).
== Octave 4.2.1 on cygwin==


== Octave 4.0.1 on cygwin==
* --awaiting confirmation of consistent instructions for Octave 4.4.0--


*'''Web-Site:''' http://cygwin.com  
*'''Web-Site:''' http://cygwin.com  
*'''Maintainer:''' Marco Atzeri  
*'''Maintainer:''' Marco Atzeri  
*'''Latest release:''' 2016-03-23
*'''Latest release:''' 2017-04-06


*Latest packages:
*Latest packages:


:octave-4.0.1-1
:octave-4.2.1-1
:Its announce on cygwin mailing list [https://cygwin.com/ml/cygwin-announce/2016-03/]
:Its announce on cygwin mailing list [https://cygwin.com/ml/cygwin-announce/2017-04/msg00017.html]


:octave-forge packages have each  a cygwin package
:octave-forge packages have each  a cygwin package
:Its announce on cygwin mailing list [http://cygwin.com/ml/cygwin-announce/2015-06/]
:Its announce on cygwin mailing list [https://cygwin.com/ml/cygwin-announce/2017-01/msg00078.html]
: Full cygwin package list is available here [https://cygwin.com/packages/]
: Full cygwin package list is available here [https://cygwin.com/packages/]
: At today 2016-03-27, 63 forge packages are available.  
: At today 2017-04-06, 64 forge packages are available.  


*To install :  
*To install :  
Line 90: Line 81:
*To build from cygwin source package, you need to install "cygport" and the relevant development libraries
*To build from cygwin source package, you need to install "cygport" and the relevant development libraries
     <nowiki>
     <nowiki>
     $ tar -xf octave-4.0.1-1-src.tar.xz  
     $ tar -xf octave-4.2.0-1-src.tar.xz  
     $ cygport octave.cygport almostall</nowiki>
     $ cygport octave.cygport almostall</nowiki>


:see cygport documentation for further info.
:see cygport documentation for further info.


=Older instructions=
=Older version instructions=
''Note that the instructions below may contain outdated links or instructions that are no longer relevant to current versions''
 
==Older MXE builds==
 
===Octave-4.2.0-4.2.2===
 
The instructions for Octave 4.2.0 - 4.2.2 are the same as for Octave 4.4.0 above. However, note that version 4.2.0 has a bug that prevents it from automatically retrieving packages from the [https://octave.sourceforge.io/packages.php Octave-Forge website] for installation or updates. Manual package installation is necessary with this version to update or install new packages on Windows.
 
To manually install a new or updated package version, the package file can be downloaded from the [https://octave.sourceforge.io/packages.php Octave-Forge website] to the working directory and can be installed using:
 
  >> pkg install package_file_name.tar.gz
 
Detailed instruction of installing Octave-Forge packages is shown at [http://wiki.octave.org/Octave-Forge Octave-Forge]
 
===Octave-4.0.3===
 
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. release installers and zip archived packages can be found at [https://ftp.gnu.org/gnu/octave/windows/ ftp.gnu.org/gnu/octave/windows/]. Unofficial 64 bit binary is available at "[http://www.tatsuromatsuoka.com/octave/Eng/Win/ File list of Octave for Windows]".
 
Known issue specific to windows version 4.0
#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)
#nan package cannot be installed by "pkg install" commands. Workaround is to execute "setenv CC gcc" before "pkg install".
 
Known issue of octave starup
# octave sometimes will fail to startup because of internal troubles. On such occasion, please try to delete .config\octave folder by which USERPROFILE environmental variable points. (One of the way to see value of USERPROFILE, startup command prompt and type "set")
 
====Packages====
Pre-built octave-forge packages are prepared for official release. If you installed Octave 4.0.3 using the executable installer you can confirm the package list by typing the command below from the Octave command prompt:
 
  >> pkg list
 
If you instead installed Octave from the .zip archive, you need to first rebuild the package list on your local machine. (The command above will produce a blank output.) Do this by typing the following command:
 
  >> pkg rebuild
 
 
Other packages can be installed by
 
  >> pkg install -forge <package name>
 
For detailed instruction of installing Octave-Forge packages is shown at [http://wiki.octave.org/Octave-Forge Octave-Forge]
 
For 64 bit binary distributed from the unofficial site, pre-built package are not prepared.
Please follow the instruction on the distribution page.
 
====gnuplot====
Current octave for windows ships a not full featured gnuplot. Therefore you cannot use the full features of gnuplot graphics toolkit 
(e.g. cannot use cairo based devise like "-dpdfcairo"). If you want use it, please use the following instruction
 
Download and install gnuplot if you do not have it. You can find the windows installer in the "[https://sourceforge.net/projects/gnuplot/files/gnuplot/ gnuplot web site for Files section]" The latest version is 5.0.3.
 
We can find path of USERPROFILE directory by
  >> getenv USERPROFILE
make an .octaverc file in USERPROFILE directory by your favorite text editor and set gnuplot_binary e.g.
 
  gnuplot_binary 'C:\Program Files (x86)\gnuplot\bin\gnuplot.exe'
 
Please do not forget to quote the path name by single quote (') if name of which has (a) white space(s).
gnuplot ver. 5 supports windows, wxt and qt terminal. On octave, windows terminal is default.
If you want change it to wxt terminal, execute
 
>> setenv GNUTERM wxt
 
You can of course describe it in .octaverc.


==MinGW ports==
==Older MinGW ports==


===Octave-4.0.0 ===
===Octave-4.0.0 ===
Line 794: Line 848:
*From gnuplot-4.4.0, the default terminal of gnuplot for windows is the wxt terminal. Some users may set the GNUTERM environmental variable for the windows terminal being default. The gnuplot for windows allows to set GNUTERM to 'win' (abbreviated form) but octave does not recognize the abbreviated form for terminal name. If one would like set GNUTERM to windows terminal, one should specify it as 'windows' (full form) but not 'win' (abbreviated form). In detail see the following thread: http://old.nabble.com/flicking-problem-again-Octave-3.2.4-mingw32-td28038688.html
*From gnuplot-4.4.0, the default terminal of gnuplot for windows is the wxt terminal. Some users may set the GNUTERM environmental variable for the windows terminal being default. The gnuplot for windows allows to set GNUTERM to 'win' (abbreviated form) but octave does not recognize the abbreviated form for terminal name. If one would like set GNUTERM to windows terminal, one should specify it as 'windows' (full form) but not 'win' (abbreviated form). In detail see the following thread: http://old.nabble.com/flicking-problem-again-Octave-3.2.4-mingw32-td28038688.html


==Octave with Visual Studio==
==Older Octave versions with Visual Studio==


Octave binaries compiled with Microsoft Visual Studio are available for download from [http://sourceforge.net/projects/octave/files/Octave%20Windows%20binaries/Octave%203.6.4%20for%20Windows%20Microsoft%20Visual%20Studio/ Octave-Forge site]. These binaries come in the form of an easy-to-use installer (created with [http://nsis.sourceforge.net/ NSIS]) and are provided in 2 flavors: pre-compiled version for Visual Studio 2008 and for Visual Studio 2010.
Octave binaries compiled with Microsoft Visual Studio are available for download from [http://sourceforge.net/projects/octave/files/Octave%20Windows%20binaries/Octave%203.6.4%20for%20Windows%20Microsoft%20Visual%20Studio/ Octave-Forge site]. These binaries come in the form of an easy-to-use installer (created with [http://nsis.sourceforge.net/ NSIS]) and are provided in 2 flavors: pre-compiled version for Visual Studio 2008 and for Visual Studio 2010.
153

edits

Navigation menu