help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mkoctfile under Windows


From: Michael Goffioul
Subject: Re: mkoctfile under Windows
Date: Mon, 10 Sep 2007 13:59:26 +0200

On 9/10/07, Christof Zeile <address@hidden> wrote:
> Michael Goffioul wrote:
> > 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.
>
> No, my octave path does not have spaces. On my German Windows
> installation, %ProgramFiles% is equivalent to "C:\Programme", unlike
> the default "C:\Program Files" on English Windows versions.
> The problem is, by the way, not with the first pair of double quotes,
> i.e. the one around the octave command, but with those around
> the command parameters.
> That means in the meantime I can make octfiles, but I cannot use
> mkoctfile.m as supplied - I had to remove those extra double
> quotes for the parameters. Cf. the attached context diff (which
> is not meant to be a patch, since it has not been tested in
> other environments).

Could you report the command that is executed (add a "disp(cmd)"
before the "system" call) and the error that is generated?

> Now I see the reason. So as long as MSVC is free there is no real
> reason to support other compilers.

Actually, there's a MinGW-based package in preparation, which will
also include the compiler.

Michael.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]