[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Windows Octave compilation
From: |
PhilipNienhuis |
Subject: |
Re: Windows Octave compilation |
Date: |
Tue, 15 Jul 2014 09:08:00 -0700 (PDT) |
Jan Tomášek wrote
>
> <snip>
> I was able to build the unstable octave(4.1.0) on my mingw. But when I try
> to run it I have this error:
> "The procedure entry point _ftelli64 could not be located in the dynamic
> link library msvcrt.dll"
Did you try to compile a 64-bit indexing Octave? (--enable-64 in the
configure options ?)
If yes I'm afraid you're a bit SOL, as building Windows binaries with 64-bit
indexing hasn't been attempted by anyone yet.
If not, then I suspect your Windows %PATH% is clobbered up by too much junk
SW in your PATH.
A while ago in IIRC the help-octave ML I gave some suggestions as to what to
do; it boils down to calling Octave from a batch script located in your
<octave>/bin subdirectory, along the lines of:
=================cut here================
@echo off
Rem Find Octave's install directory through cmd32.exe variables.
Rem This trick finds the location where the batch file resides.
Rem Note: the result ends with a backslash & points to OCTAVE_HOME/bin
set OCT_HOME_BIN=%~dp0
Rem Set up PATH. Make sure the Octave bin subdir
Rem comes first. Use system environment variables for the
Rem Windows system dirs.
Rem Ghostscript is still an issue, I've left my setup for it
Rem in the line below:
set
PATH=%OCT_HOME_BIN%;%windir%\system32;%windir%;%windir%\system32\wbem;C:\Programs\gs\gs9.04\bin
Rem Start Octave (this detaches octave-gui and immediately
Rem returns):
start octave-gui.exe
Rem Close the batch file's cmd32.exe window
exit
================= /cut ===============
...(Note the Ghostscript line that has to be adapted to your system)
...and make a desktop / Start Menu shortcut for Octave pointing to this
batch file.
This batch file cleans up the Windows PATH in Octave's process slots to only
that stuff that is essential for Octave to run (it'll leave the PATH
untouched for all other progs).
Philip
--
View this message in context:
http://octave.1599824.n4.nabble.com/Re-Windows-Octave-compilation-tp4665267p4665524.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.
- Re: Windows Octave compilation, (continued)
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/11
- RE: Windows Octave compilation, John D, 2014/07/11
- Re: Windows Octave compilation, John W. Eaton, 2014/07/11
- RE: Windows Octave compilation, John D, 2014/07/11
- Re: Windows Octave compilation, John W. Eaton, 2014/07/11
- RE: Windows Octave compilation, John D, 2014/07/11
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/14
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/14
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/14
- Re: Windows Octave compilation, Jan Tomášek, 2014/07/15
- Re: Windows Octave compilation,
PhilipNienhuis <=
- Re: Windows Octave compilation, John W. Eaton, 2014/07/15
- Re: Windows Octave compilation, PhilipNienhuis, 2014/07/15
- Re: Windows Octave compilation, John W. Eaton, 2014/07/15
- Re: Windows Octave compilation, PhilipNienhuis, 2014/07/15
- RE: Windows Octave compilation, John D, 2014/07/15
- RE: Windows Octave compilation, Jan Tomášek, 2014/07/16
- RE: Windows Octave compilation, tmacchant, 2014/07/17
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/19
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/19
- RE: Windows Octave compilation, Jan Tomášek, 2014/07/15