Re: MSVC Octave (2.9.12-3)

[David Bateman]

Marcel Graf wrote:
> Michael Goffioul <michael.goffioul <at> gmail.com> writes:
> 
>> On 6/5/07, Tatsuro MATSUOKA <tmacchant <at> yahoo.co.jp> wrote:
>>> 2. Mkoctfile still fails in the link process.
>>> We still need remove unrequried link option like
>>> '-llapack' manually.
>> Could you report the compilation error you get? Normally, all 
>> required .lib files have been included.
>>
>> Michael.
> 
> Hello
> 
> I installed octave-2.9.12-3-setup.exe and
> can confirm that the adding the octave\lib directory to LIB is still
> needed. In order to successfully compile & use hello.cc, I used:
> ---
> REM needed to find cl & link
> call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat"
> 
> REM needed to find ws2_32.lib, kernel32.lib, ...
> call "C:\Program Files\Microsoft Platform SDK for
> Windows Server 2003 R2\SetEnv.Cmd"

Yes, I'd like to see some well documented means of using MSVC with octave..

> 
> REM needed to find lapack.lib, ...
> call set LIB=C:\Octave\lib;%LIB%

I think this is now fixed and will be in the next release..

> 
> call "C:\Octave\bin\oct
> ---
> and then "mkoctfile hello.cc" .
> 
> Similarly, I tried with a mex file, which compiles & links as well
> (mex mexfile.c), but can not be run. Indeed, the mexfile.mex file
> does not contain the string "mexFunction" at all - thats what octave
> is looking for, right?
> 

I think the patch

http://octave.cvs.sourceforge.net/octave/octave-forge/admin/Windows/msvc/mkoctfile.cc.in?r1=1.7&r2=1.8

addresses this. The mexFunction was not exported.. So this too should be
fixed in the next release.. These are testing release :-).. Thanks for
the feedback..

Cheers
David