Re: [Kaldi-developers] Kaldi on Windows

[Jan T. <af...@ce...>]

Hi, there was a discussion about getting Kaldi compiled under VS (various
versions) two weeks ago (or so).
The practical experience is that getting the VS project loaded(opened) is
the least of the problems. You can find the discussion in the
kaldi-{devel,users} mail archives on sf.net

Y.

On Mon, Mar 2, 2015 at 3:53 PM, Daniel Povey <dp...@gm...> wrote:

> Hi,
> If you are going to use cygwin, then it is best to just compile it in
> cygwin.  If you compile using Visual Studio, the binaries won't work
> correctly- I forget whether it relates to how newlines are handled, how
> pipes work, or some other reason.  In any case, Visual Studio is quite
> buggy- some problems were reported recently on one of these lists.
> Dan
>
>
> On Mon, Mar 2, 2015 at 3:49 PM, Kirill Katsnelson <
> kir...@sm...> wrote:
>
>>  Thank you Dan! I hope cygwin will take care of the script part, unless
>> there are exotic used like unix domain sockets, procfs etc.
>>
>>
>>
>> -kkm
>>
>>
>>
>> *From:* Daniel Povey [mailto:dp...@gm...]
>> *Sent:* 2015-03-02 1127
>> *To:* Kirill Katsnelson
>> *Cc:* kal...@li...
>> *Subject:* Re: [Kaldi-developers] Kaldi on Windows
>>
>>
>>
>> I confirmed on both lists.  Replying to kaldi-developers and just bcc'ing
>> kaldi-users.
>>
>> It would be great if you could improve the Windows build for us.
>>
>> However, Kaldi scripts are dependent on things like bash, and it won't
>> work on Windows.  So ultimately it will not make sense for you to train on
>> Windows- the cost of your time will be more than the cost of a new
>> machine.  That being said, I would appreciate better Windows build scripts
>> (main use case is deployment of recognition on Windows).
>>
>> Dan
>>
>>
>>
>>
>>
>> On Mon, Mar 2, 2015 at 2:05 PM, Kirill Katsnelson <
>> kir...@sm...> wrote:
>>
>> Hi,
>>
>> I am trying to compile and use Kaldi on Windows. The perl script that
>> comes in the distribution does not produce very useful results, since
>> VS2013 has a trouble opening (opening, not compiling!) the resulting
>> monster solution of 600+ projects. It does not support CUDA also.
>>
>> I approached the problem from the square one and am writing msbuild
>> scripts with the support for CUDA, MKL and Intel C++ compiler.
>>
>> Is there any interest in supporting Kaldi build on Windows in the
>> mainline distribution? For me, a practical consideration in this decision
>> was the cost of building an extra machine with CUDA hardware and Intel
>> software just for Kaldi, while my Windows machine already has all this.
>>
>> Is kal...@li... a closed list? I send a
>> subscription request to the both lists, but got a confirmation from the
>> -users@ list only.
>>
>>  -kkm
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub
>> for all
>> things parallel software development, from weekly thought leadership
>> blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Kaldi-developers mailing list
>> Kal...@li...
>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers
>>
>>
>>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Kaldi-developers mailing list
> Kal...@li...
> https://lists.sourceforge.net/lists/listinfo/kaldi-developers
>
>