Hi, list.
I am interested in building Octave by myself using MSVC.
I have found wiki article http://wiki.octave.org/Octave_for_Windows#Building_from_source
last paragraph of which states
"In addition to the instructions provided in the Octave manual, a basic toolkit for building Octave in windows using the MSVC compiler has been produced by Michael Goffioul. It consists of a set of scripts that can be used to compile Octave and its dependencies.
A pre-compiled (with VS2010) version of everything has also been provided, so it is not necessary to recompile everything from scratch. The files can be found at: http://dl.dropbox.com/u/45539519/octave-build2.zip and http://dl.dropbox.com/u/45539519/VC10Libs.zip"
And I have found recent mail from Michael Goffioul in this list
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2013-February/032251.html
about the same topic.
I want to ask two questions:
1) Does this script/makefile set ( from 1st dropbox link ) regularily updated or maybe there is some repository with this scripts?
It's not regularly updated nor available from some repository. But that archive available in my Dropbox folder are fairly up to date.
2) Is there any detailed instructions/readme/howto about using these scripts?
No. The entry point is the script build.sh, which is typically called as:
./build.sh --msvc --prefix=/whatever/prefix/you/want/to/use <module-name>
For the prefix, decide on a location where you will install all compiled stuff. If you installed the VC10Libs archive, then use the location where you unpacked it. The module names corresponds to subdirs in the modules/ directory. There's some dependency checking, but it won't auto-compile required dependencies for you. You need to compile things in sequence. Additional build.sh arguments are:
-k : do not remove build directory (if build fails, it is always kept)
-jN: passed directly to "make", to parallelize compilation
The requirements to use the scripts are a fully functional MSYS shell with VS2010 development tools readily available. The simplest way to achieve this is to hack your msys.bat and "call" the MSVC setup script, vcvarsall.bat, located somewhere in VS2010 installation directory (this is briefly explained at the bottom of this page [1]).