Re: [Kaldi-developers] [Kaldi-users] Kaldi compiles now under VS 2013

[Kirill K. <kir...@sm...>]

I actually have kaldi more or less fully working under Windows. It compiles with either VS 2013 or ICL, MKL and CUDA. I completely redid the build system, so it does not depend on VS being used and loading 600+ projects. 

I did not get a noticeable performance gain from ICL vs MSC, and ICL in optimizing mode compiles the code up to 5 times longer than the MSC. I think the reason is that kaldi uses a matrix library for all sizable work. 

The code needs certain patches and Cygwin runtime configuration tricks to get it working. The main problems are 1) pathnames, as shell scripts pass unix-style paths to kaldi programs and 2) binary files on stdin/out, which get promptly corrupted by LF -> CR LF expansion on output unless configured. Most kaldi *bin/ programs already apply the setting, but OpenFST tools do not.

However, I ran both librispeech and tedlium sets through to completion. It was a painful but a rewarding exercise in understanding the structure and guts of the toolkit.

I tried both Paul's 1.3.x (do not remember the value of x off the top of my head) and 1.4.1 ports of OpenFST. The part required by Kaldi works in both. I stayed conservative with 1.3 in my tests though. Both versions required a couple of changes missed by the original patcher.

I have all changes in github, and I was holding my patches until the repo is migrated, so that they are easy to peer-review. If there is an interest in running it before it's integrated, let me know. I need to both update the branch to the latest code and write a configuration guide. 

 -kkm

> -----Original Message-----
> From: Jan Trmal [mailto:jt...@gm...]
> Sent: 2015-05-06 1415
> To: kal...@li...; kaldi-
> us...@li...
> Subject: [Kaldi-users] Kaldi compiles now under VS 2013
> 
> All, just to have it here in case someone actually search the list
> before asking:
> I was able to compile Kaldi under VS 2013 and OpenFST(Win)1.3.4 (which
> I forked from Paul Dixon's 1.3.3, did some more fixes and upgraded to
> 1.3.4 -- but the kudos should go to Paul). The changes were committed
> to the repository, so it should be available to everyone.
> I 'm planning to figure out if it's possible to add support for VS2015
> and potentially OpenFST 1.4.x OpenFST 1.4.x needs C++11, which, to my
> knowledge, is partial at best in VS2015, so we will see...
> 
> BTW: I'm not sure if anyone will be able to maintain/fix the codes to
> be "compilable" under MS VS.
> 
> In case of troubles (and if you really really need Kaldi in VS), use
> the Intel C++ compiler. It seems that it adheres to the standard
> C++/C++11
> -- (which is not the case for VS)
> 
> y.