Re: PATH: default fortran naming scheme when using F2C

[Michael Goffioul]

David Bateman a écrit :
> > There's also the question of what to put into such a package in terms of
> > external
> > libraries (FFTW, SparseSuite...), M-packages (octave-forge, which does not
> > compile well under MSVC) and so on. 
> >     
>
> Packages in octave-forge can and should be patched as needed. However
> worry about the octave core first and the rest will follow. It might be
> interesting to see how the package manager itself performs under an MSVC
> compiled version of octave.
>   

Depending on the dependency on external utilities, it might not work 
well. Which package
manager are you referring to? pkg.m? I suspect that it rely on the 
availability of an
underlying POSIX shell; hence it won't work.

> One concerned I'd have with this setup, is that how do we make a version
> of octave capable of building oct- or mex-files? We can't distribute
> MSVC ourselves and so we have to have instructions of how to go about
> getting a setup capable of building oct- and mex-files easily accessible.
>   

For the time being, mkoctfile relies on a shell, hence you'd need at 
least MSYS. A few days ago,
I posted a C++ version of mkoctfile that get rid of the need of a shell 
and could be used directly
from the Windows command prompt. Besides that, the gcc-like wrapper can 
be packaged with
octave, but of course not the compiler.

> > For the moment, I'm compiling octave
> > against FFTW, GPLK, a hacked version of SparseSuite and readline, because
> > it suits my needs. But you might think about other configurations.
> >     
>
> The only thing I feel missing from that is ATLAS, which really is
> needed. We'd also need to package with a gnuplot binary to allow
> plotting to work correctly out of the box, So there might be so path
> issues to address. In short the packaging might be a little more than
> just taking octave.exe and making a NSIS installer.
>   

I tried to compile ATLAS with my setup, but gave up after a few hours. 
The build system seems
quite complex and I didn't want (nor had the time) to dig into it. Note 
that I also tried under MinGW
but it failed at some point.

Concerning gnuplot, I'd say you have 2 options:
1) either install gnuplot somewhere and put the bin/ directory in the 
PATH at installation time
2) or install gnuplot somewhere and modify the site octaverc with a 
gnuplot_binary command
In the end, it can be done by the installer.

> Cheers
> David
>
>
>