Re: mkoctfile under Windows

[Michael Goffioul]

On 9/7/07, Christof Zeile <address@hidden> wrote:
> Summary:
> * Something goes wrong with the double quotes in mkoctfile.m.

Did you install octave in a location containing space? mkoctfile.m
cannot handle this correctly yet (thanks MS for using an obviously
inconsistent double-quote handling...). However, calling mkoctfile.exe
from command prompt should work OK, even if octave path contains
spaces.

> * I need to call vcvarsall.bat to set the MSVC paths.

This is "normal" in the sense that there's no standard include or lib
directory under Windows. You have to tell the compiler where to find
headers and libraries explicitely. In general,  mkoctfile assumes a
well-configured compiling environment is available, there's no auto-
detection or auto-configure mechanism.

> * Somehow I have to set the include and library paths for the SDK
>   manually.

Again, no standard include.lib directory. When using express edition,
Platform SDK is a separate package, so you need additional configuration.
As Tatsuro mentioned it, the SDK comes with it's own configure script
SetEnv.cmd. This script is able to detect the MSVC compiler and setup
everything (you don't need to call vcvarsall.bat from MSVC directory).

Michael.