Building on Microsoft Windows: Difference between revisions

Jump to navigation Jump to search
→‎Building natively (MSYS2): Don't use cross-compilers
(→‎Building natively (MSYS2): Add command for symlinking octave-svgconvert.exe)
(→‎Building natively (MSYS2): Don't use cross-compilers)
(12 intermediate revisions by the same user not shown)
Line 18: Line 18:
If you want to contribute changes to C++ files or are interested in testing the latest development or (unreleased) stable release, you can build Octave from source.
If you want to contribute changes to C++ files or are interested in testing the latest development or (unreleased) stable release, you can build Octave from source.


There is currently no maintained way to build Octave on Windows directly. But it is still possible to build Octave on Windows machines using virtual machines or Microsoft's Windows Subsystem for Linux.
It seems to be possible to build Octave natively on Windows with the MSYS2 shell. (Be aware that this might take some time.) It is also possible to build Octave on Windows machines using virtual machines or Microsoft's Windows Subsystem for Linux. The latter is the preferred way to build Octave.
 
Building Octave natively on Windows is experimental! The only supported way of creating Windows binaries of Octave is cross-building with MXE Octave ([[Windows Installer]]).


==Virtual Machine==
==Virtual Machine==
Line 93: Line 95:
Use the "MSYS2 MinGW 64bit" shell for building Octave.
Use the "MSYS2 MinGW 64bit" shell for building Octave.


The following command can be used to install the necessary and optional build dependencies in MSYS2:
The following command can be used to install the necessary and optional build and run-time dependencies in MSYS2:
<pre>pacman -S base-devel mingw-w64-x86_64-toolchain mingw-w64-x86_64-lapack mingw-w64-x86_64-openblas mingw-w64-x86_64-pcre \
<syntaxhighlight lang="bash">pacman -S base-devel mingw-w64-x86_64-toolchain mingw-w64-x86_64-lapack mingw-w64-x86_64-openblas mingw-w64-x86_64-pcre \
   mingw-w64-x86_64-arpack mingw-w64-x86_64-curl mingw-w64-x86_64-cvode mingw-w64-x86_64-fftw mingw-w64-x86_64-fltk mingw-w64-x86_64-gl2ps mingw-w64-x86_64-glpk mingw-w64-x86_64-ghostscript mingw-w64-x86_64-gnuplot mingw-w64-x86_64-graphicsmagick mingw-w64-x86_64-hdf5 mingw-w64-x86_64-libsndfile mingw-w64-x86_64-portaudio mingw-w64-x86_64-qhull mingw-w64-x86_64-qrupdate mingw-w64-x86_64-qscintilla mingw-w64-x86_64-qt5 mingw-w64-x86_64-rapidjson mingw-w64-x86_64-suitesparse \
   mingw-w64-x86_64-arpack mingw-w64-x86_64-curl mingw-w64-x86_64-fftw mingw-w64-x86_64-fltk mingw-w64-x86_64-gl2ps mingw-w64-x86_64-glpk mingw-w64-x86_64-ghostscript mingw-w64-x86_64-gnuplot mingw-w64-x86_64-graphicsmagick mingw-w64-x86_64-hdf5 mingw-w64-x86_64-libsndfile mingw-w64-x86_64-portaudio mingw-w64-x86_64-qhull mingw-w64-x86_64-qrupdate mingw-w64-x86_64-qscintilla mingw-w64-x86_64-qt5 mingw-w64-x86_64-rapidjson mingw-w64-x86_64-suitesparse mingw-w64-x86_64-sundials \
  libutil-linux-devel \
   git mercurial mingw-w64-x86_64-ccache mingw-w64-x86_64-icoutils mingw-w64-x86_64-librsvg texinfo \
   ccache git mercurial mingw-w64-x86_64-icoutils mingw-w64-x86_64-librsvg texinfo</pre>
  unzip zip</syntaxhighlight>


To create scripts that allow it to use ccache easily (for most of the compilers in MSYS2), one can use the following commands:
Using ccache is optional. It speeds up compilation time but needs several GiB free disk space for its cache. If disk space is an issue, this step can be skipped. To prepend the path to the ccache helper scripts to the front of the PATH variable, add the following line near the end of the {{Path|.bash_profile}} file in your MSYS2 {{Path|$HOME}} directory:
<pre>cd /usr/lib/ccache/bin
<syntaxhighlight lang="bash">export PATH="/mingw64/lib/ccache/bin:$PATH"</syntaxhighlight>
scripts=(c++ cc cpp gcc g++ gfortran x86_64-w64-mingw32-g++ x86_64-w64-mingw32-c++ x86_64-w64-mingw32-gcc x86_64-w64-mingw32-gfortran)
 
for fn in ${scripts[*]}; do
Additionally, add the following line to the {{Path|.bash_profile}} file in your MSYS2 {{Path|$HOME}} directory to allow successfully calling programs from perl scripts:
  echo -e '#!/bin/bash\n\nccache /mingw64/bin/'$fn' "$@"' > $fn
<syntaxhighlight lang="bash">export PERL5SHELL="bash -l -c"</syntaxhighlight>
done</pre>
Additionally, add the path to these helper scripts to the front of the PATH variable by adding the following line near the end of the {{Path|.bashrc}} file in your MSYS2 {{Path|$HOME}} directory:
<pre>export PATH="/usr/lib/ccache/bin:$PATH"</pre>


Like installing the build dependencies, this has to be done only once.
Like installing the build dependencies, this has to be done only once.


To build from the development sources, check out the Mercurial repository and run the {{Path|bootstrap}} script:
To build from the development sources, check out the Mercurial repository and run the {{Path|bootstrap}} script:
<pre> hg clone https://www.octave.org/hg/octave && \
<syntaxhighlight lang="bash">hg clone https://www.octave.org/hg/octave
cd octave && \
cd octave
./bootstrap</pre>
./bootstrap</syntaxhighlight>
 
Create a sub-directory to avoid building in the source tree:
<syntaxhighlight lang="bash">mkdir -p .build
cd .build</syntaxhighlight>


Configure with the following flags:
Configure with the following flags:
<pre>../configure CC="x86_64-w64-mingw32-gcc" CXX="x86_64-w64-mingw32-g++" F77="x86_64-w64-mingw32-gfortran" PORTAUDIO_LDFLAGS="-LC:/msys64/mingw64/lib -LC:/msys64/usr/lib" --disable-docs ac_cv_search_tputs=-ltermcap</pre>
<syntaxhighlight lang="bash">../configure \
  --disable-docs \
  ac_cv_search_tputs=-ltermcap</syntaxhighlight>


And build with the following flags:
And build with the following command:
<pre>make all -j8 FLTK_LIBS="-lfltk_gl -lopengl32 -lglu32 -lfltk -lpthread" PERL5SHELL="bash -l -c"</pre>
<syntaxhighlight lang="bash">make all -j8</syntaxhighlight>


Octave doesn't run correctly from the MSYS2 shell due to issues with readline. To be able to work with it anyway, install it with the following commands:
Octave doesn't run correctly from the MSYS2 shell due to issues with readline and backslash as a file separator. To be able to work with it anyway, install it with the following commands (from the MSYS2 shell in {{Path|.build}}):
<pre>make install
<syntaxhighlight lang="bash">make install
ln -sf /mingw64/libexec/octave/7.0.0/exec/x86_64-w64-mingw32/octave-gui.exe /mingw64/bin/octave-gui.exe
ln -sf /mingw64/libexec/octave/7.0.0/exec/x86_64-w64-mingw32/octave-gui.exe /mingw64/bin/octave-gui.exe
ln -sf /mingw64/libexec/octave/7.0.0/exec/x86_64-w64-mingw32/octave-svgconvert.exe /mingw64/bin/octave-svgconvert.exe</pre>
ln -sf /mingw64/libexec/octave/7.0.0/exec/x86_64-w64-mingw32/octave-svgconvert.exe /mingw64/bin/octave-svgconvert.exe</syntaxhighlight>
The latter two symlinks are only needed when building the GUI (i.e., Qt is not disabled).


Start Octave from a CMD shell (or with a batch script) with the following content (assuming MSYS2 was installed in its default location):
Start Octave from a CMD shell (or with a batch script) with the following commands (assuming MSYS2 was installed in its default location):
<pre>set PATH=C:\msys64\mingw64\bin;C:\msys64\usr\bin;%PATH%
<syntaxhighlight lang="batch">set PATH=C:\msys64\mingw64\bin;C:\msys64\usr\bin;%PATH%
set MSYSTEM=MINGW64
set MSYSTEM=MINGW64
set TERM=cygwin
set TERM=cygwin
Line 133: Line 139:
set GS=gs.exe
set GS=gs.exe
set PERL5SHELL=bash -l -c
set PERL5SHELL=bash -l -c
octave-gui --gui</pre>
octave-gui --gui</syntaxhighlight>
If Octave was built without GUI, there won't be an {{Path|octave-gui}} executable. In that case, replace the last line with <code>octave-cli</code>.


=Footnotes=
=Footnotes=
216

edits

Navigation menu