Re: [OctDev] Re: A new standalone octave for 2.1.60, and setup.

[Paul K. <pki...@us...>]

So you rebuilt from scratch?  Or did you use my version?
Obviously the former since my version had octave-forge
already installed in /opt/octave-2.1.60/site/octave-forge.

Did you use octave.nsi?  What changes did you make?

What did you use for the cygwin environment?  The one I
provided?  Have you tested it yet?  Did it work?

My lapack.dll includes blas.  The idea was to make
platform specific lapack-atlas-arch.dll files and copy
them over lapack.dll at install time.  Note that we
should have a copy of lapack.dll in lapack-base.dll
in case there is any problems.

I don't know why the FILE command isn't working.

- Paul

On Oct 28, 2004, at 2:31 AM, Ole Jacob Hagen wrote:

> Hi, Paul.
>
> During the late hours tonight I managed to make a standalone 
> Octave-2.1.60 with Octave-forge and win32-version of Gnuplot.
>
> Now I've just have to solve the symlinks of the oct-files, and go 
> through all the oct-files.
>
> I didn't get a "permission denied" error when I quit Octave.
>
> I've installed octave-forge into Octave's /share and libexec as done 
> on Linux-systems.
> Why this doesn't happen automatically in cygwin environment, I don't 
> know.
> But it should, right?
>
> Thanks for helping out, Paul.
> Appreciate it a lot.
>
> This didn't work on the new version of NSIS (2.0):
>
>    FILE /r "${ROOT}\opt\octave-${VERSION}\bin\*.*"
>
> I should have a standalone application this day.
>
> Need a suggestion:
>
> Should I use ATLAS and/or BLAS packages?
>
> Cheers,
>
> Ole J.
>