Re: RC1 Candidate (windows 64, msvcr100.dll)

[Markus Mützel]

Am 29. Januar 2019 um 04:05 Uhr schrieb "Tatsuro MATSUOKA":
> I also met application error (0xc000007b) octave-5.0.90 for windows 
> from  alpha.gnu.org/gnu/octave/.
> 
> My path on windows 10
> 
> C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Programs\gs\gs9.23\bin;C:\Programs\gs\gs9.23\lib;C:\Program
>  Files (x86)\Windows Kits\10\Windows Performance 
> Toolkit\;C:\WINDOWS\System32\OpenSSH\;C:\Programs\plzip-1.5-rc2.win;;C:\Program
>  Files (x86)\Microsoft VS Code\bin;C:\Users\MATSUOKA 
> LAB\AppData\Local\Microsoft\WindowsApps;;C:\texlive\2018\bin\win32
> 
> 
> From cmd I erase the path.
> set PATH=
> 
> 
> and execute octave.vbs
> then
> octave-gui.exe claims  no msvcr100.dll.
> 
> Only 32 bit version exists on my system.
> I installed microsoft visual c++ 2010 service pack 1 redistributable package 
> and Problem is solved.
> 
> On 64bit octave-4.4.1 for windows runs without 64bit version msvcr100.dll.
> 
> What is changed from 5.0.90?
> 
> (Note that octave-cli.exe runs without 64bit version msvcr100.dll for 
> octave-5.0.90)
> 
> Tatsuro

Running octave-cli.exe through Dependency Walker shows that the dependency on 
msvcr100.dll is through qt5core.dll --> icuin63.dll.
Can we bundle the redistributable package in the nsis installer or somehow else 
tell that we dependent on MS Visual C++ 2010?

Alternatively, can we compile ICU without the dependency on MS Visual C++?

I also wonder if the reports of people not being able to start newer versions 
of Octave is related to this.

Markus