Re: Compiling octave with MSVC

[John W. Eaton]

On 10-Oct-2006, Søren Hauberg wrote:

|    Does this give you a fully functional version of octave running on 
| Windows?

That's a good question.  Specifically, what happens for the system
function?  I think you need at least a minimally functional Bourne
shell environment to support the things like

  [status, output] = system(["cd " src " ;./configure --prefix=" desc.dir]);

in pkg.m.  There are other instances where Octave depends on external
commands, at least in the following files (there may be more in Octave
Forge):

  audio/playaudio.m
  audio/record.m
  audio/setaudio.m
  image/image.m
  miscellaneous/bug_report.m
  miscellaneous/unix.m
  miscellaneous/tar.m
  miscellaneous/untar.m
  miscellaneous/doc.m
  miscellaneous/mkoctfile.m
  miscellaneous/unzip.m
  miscellaneous/dos.m
  plot/print.m

In any case, MinGW can handle the compiling of Octave without needing
to link to a compatibility library like Cygwin, so what is the
advantage of using MSVC, unless you need to link with some other C++
code that was compiled with MSVC?

jwe