Readme for different versions are slightly different. I would recommend leaving the multiple folders.
Octave-3.6.2-mingw + octaveforge pkgs
1. Files for manual installation
a. Octave-3.6.2-mingw binaries tree
Octave362_gcc462_20120609.7z - MD5:1FA1F6191C151D527830722F71822312
This is a 7z archive which includes a directory tree of all the binaries and
libraries required for a complete octave installation (excluding octaveforge
packages)
The archive includes:
mingw32 + msys tool chain
gnuplot-4.6.0
fig2dev-3.2.5c
ghostscript-9.0.5
pstoedit-3.60
Optional blas libs replacements:
<your_install_dir>\bin directory includes several libblas.dll.<libblas_source> where <libblas_source> is a text extension which describes the source of the library
libblas.dll.ref - reference blas implementation, very slow but most stable
libblas.dll.OpenBLAS-v0.1.0-0-09f74f6_dynamicarch - Openblas based, up to 2 threads, detects cpu architecture and selects respective lib
libblas.dll.OpenBLAS-v0.1.0-0-09f74f6_dynamicarch_nt4 - Openblas based, up to 4 threads, detects cpu architecture and selects respective lib
libblas.dll.OpenBLAS-v0.1.0-0-09f74f6_nehalem - Openblas based, up to 2 threads, tuned for nehalem cpu architecture
libblas.dll.OpenBLAS-v0.1.0-0-09f74f6_nehalem_nt4 - Openblas based, up to 4 threads, tuned for nehalem cpu architecture
libblas.dll.OpenBLAS-v0.1.0-0-09f74f6_core2 - Openblas based, up to 2 threads, tuned for core2 cpu architecture
libblas.dll.OpenBLAS-v0.1.0-0-09f74f6_core2_nt4 - Openblas based, up to 4 threads, tuned for core2 cpu architecture
libblas.dll.altas-3.8.4_ht-pentium - ATLAS based libblass, tuned for older ht-pentium (compiled by Tatsuro Matsuka)
libblas.dll.altas-3.8.4_corei5 - ATLAS based libblass, tuned for older core i5 cpu (compiled by Tatsuro Matsuka)
Default installed libblass.dll is libblas.dll.OpenBLAS-v0.1.0-0-09f74f6_dynamicarch which intended to automatically detect the cpu architecture and select a respectivly tuned library
In case the default library is not properly functioning on the actual cpu, or you wish to explore the performance with another liblas.dll.<libblas_source> it can be manually selected to replace the default one:
delete <your_install_dir>\bin\libblas.dll
make a copy of the desired <your_install_dir>\bin\libblas.dll.<libblas_source>
rename the copy of the desired <your_install_dir>\bin\libblas.dll.<libblas_source> to libblas.dll
Maintainer: Nitzan Arazi
Latest update: 2012-06-09
b. Octaveforge pkgs, built for Octave-3.6.2-mingw
Octave3.6.2_gcc4.6.2_pkgs_20120613.7z - MD5:C8BADBA76190DD71978D87A09AB9250B
This is a 7z archive which includes additional binaries and libraries for a
set of octaveforge packages.
The included packages are:
actuarial-1.1.0
ad-1.0.6_patched
audio-1.1.4
benchmark-1.1.1
bim-1.0.2
bioinfo-0.1.2
civil-engineering-1.0.7
combinatorics-1.0.9
communications-1.1.1_patched
control-2.3.51
data-smoothing-1.3.0
dataframe-0.9.1
econometrics-1.0.8
fenv-0.1.0
financial-0.4.0
fpl-1.2.0
fuzzy-logic-toolkit-0.3.0
ga-0.10.0
general-1.3.1
generate_html-0.1.4
geometry-1.5.0
gnuplot-1.0.1
gpc-0.1.7
gsl-1.0.8
ident-1.0.7
image-1.0.15
informationtheory-0.1.8
integration-1.0.7_svn20120128
io-1.0.19
irsa-1.0.7
java-1.2.8_patched
linear-algebra-2.2.0_patched
mapping-1.0.7
mechanics-1.2.0
miscellaneous-1.1.0
missing-functions-1.0.2
msh-1.0.2
multicore-0.2.15
nan-2.5.5
nlwing2-1.2.0
nnet-0.1.13
nurbs-1.3.6
ocs-0.1.3_svn20120128_patched
octclip-1.0.0
octgpr-1.2.0
odebvp-1.0.6
odepkg-0.8.2
optim-1.1.0_patched
optiminterp-0.3.4_svn20120128_patched
outliers-0.13.9
physicalconstants-0.1.7
plot-1.1.0
quaternion-2.0.0
queueing-1.1.0
secs1d-0.0.9
secs2d-0.0.8
secs3d-0.0.1
signal-1.1.3
simp-1.1.0
sockets-1.0.7_svn20120128_patched
specfun-1.1.0
special-matrix-1.0.7
spline-gcvspl-1.0.8
splines-1.0.7
statistics-1.1.3
strings-1.1.0_patched
struct-1.0.10
symband-1.0.10
symbolic-1.1.0
tcl-octave-0.1.8
time-2.0.0
tsa-4.2.4
video-1.0.2_patched
vrml-1.0.12_svn20111014_patched
windows-1.1.0
xraylib-1.0.8
zenity-0.5.7
Maintainer: Nitzan Arazi
Latest update: 2012-06-13
2. Manual installation instructions
Create an installation directory of which doesn't have space chars (i.e.
C:\Octave\Octave3.6.2_gcc4.6.2\). This directory is referred hereafter as
<your_install_dir>.
Extract the complete directories tree from Octave3.6.2_gcc4.6.2_20120303.7z
to the installation directory keeping the original directory structure as in
Copy octave3.6.2_gcc4.6.2.lnk to any convenient location and edit its
properties respectively to point to <your_install_dir>\bin\octave.exe and
<your_install_dir>\share\octave\3.6.2\imagelib\octave-logo.ico as an icon
Copy octave3.6.2_gcc4.6.2_docs.lnk to any convenient location and edit its
properties respectively to point to <your_install_dir>\doc\octave and
<your_install_dir>\share\octave\3.6.2\imagelib\octave-logo.ico as an icon.
At this point you can:
a. Launch and use octave by double-clicking the copied
octave3.6.2_gcc4.6.2.lnk
b. Access and browse the documentation files by double-clicking the copied
octave3.6.2_gcc4.6.2_docs.lnk
3. Manual installation instructions for the Octave-forge packages
Extract the complete directories tree from
Octave3.6.2_gcc4.6.2_pkgs_20120303.7z to the installation directory
(<your_install_dir>) keeping the original directory structure as in the
In order to update octave_packages database with your installation tree and
auto-load most packages (excluding 'ad' and 'windows' which may crash octave
when loaded and 'clear all' is executed), launch Octave and execute the
following 3 rebuild commands from the octave console:
pkg rebuild -auto
pkg rebuild -noauto ad windows
pkg rebuild -noauto nan % shadows many statistics functions
pkg rebuild -noauto gsl % shadows some core functions
pkg rebuild -auto java
Last pkg rebuild command is required in order for the java pkg entry to be
moved to the top of <your_install_dir>\share\octave\octave_packages db file
- thus java pkg is loaded before io pkg is loaded, and io pkg related jars
are added to java class path.
You can optionally adjust your installed packages status per your specific
needs and usage by executing the following commands:
a. To interactively load or unload a package
pkg load <pkg_name>
or
pkg unload <pkg_name>
b. To disable auto-load for specific pkg <pkg_name>
pkg rebuild -noauto <pkg_name>
c. To enable auto-load for specific pkg <pkg_name>
pkg rebuild -auto <pkg_name>
d. To completely uninstall a package
pkg uninstall <pkg_name>
4. Optional installation of Notepad++ as an editor (recommended)
Download recent Notepad++ installation package from
Edit <your_install_dir>\share\octave\site\m\startup\octaverc and un-comment
the line which sets octave default editor:
EDITOR('C:\Program Files\Notepad++\notepad++.exe');
Note: You may adjust the above line for the location of notepad++.exe as
installed on your system.
5. Troubleshooting
Upon launching, some warnings may be displayed. These warnings can be
ignored.
Following warnings are about missing external tools which may reduce some of
the functions of some packages. These external tools are not provided by the
7z archives in sourceforge.
warning: gmsh does not seem to be present some functionalities will be
disabled
warning: dx does not seem to be present some functionalities will be
disabled
Following warning is about fstat function of the statistics package that
overloads the old (to be deprecated) fstat function of octave-3.6.2
warning: function
C:\Octave\3.6.2_gcc-4.6.2\share\octave\packages\statistics-1.1.3\fstat.m
shadows a core library function
On Wed, Jun 13, 2012 at 3:01 PM, Carnë Draug
<address@hidden> wrote:
On 13 June 2012 10:14, nitnit <address@hidden> wrote:
> Hello all,
>
> I have built and packaged mingw octave and octaveforge pkgs binaries (based
> on Tatsuro's libs as usual).
>
> Octave362_gcc462_20120609.7z
> https://docs.google.com/open?id=0B543KlC8JEaZTk84Y3hfUUIxeGM
> md5:1FA1F6191C151D527830722F71822312
>
> Octave3.6.2_gcc4.6.2_pkgs_20120613.7z
> https://docs.google.com/open?id=0B543KlC8JEaZeS01bGVETjBUM0k
> md5:C8BADBA76190DD71978D87A09AB9250B
>
> Please test.
>
> Carne - please upload to octaveforge.
Done. Could you prepare a README file for the directory? Or if they
are always the same, should I move all MinGW installers to the same
directory?
Also, you'll probably want to announce this on the octave-help and
octave forge mailing lists.
Carnë