Re: [Kaldi-developers] Compiling Kaldi on windows

[Jan T. <jt...@gm...>]

Ona last thing that could be tried,  if one really wants to use visual
Studio,  is actually using Intel C/C++,  which has direct integration into
VS,  including the debugger and profiler.  It does not support  integration
into VSExpress,  though  (such is some Microsoft's policy).

BTW,  just for the sake of having it archived in this context: even in
Windows you can use cygwin/mingw to compile kaldi using gcc.

Y.
On Feb 20, 2015 9:32 PM, "Daniel Povey" <dp...@gm...> wrote:

>
> This thing where it can't resolve int32 is a bug in the namespace lookup
> in the compiler, where if a template is evaluated in a different namespace
> from where it was declared, it adds the namespace where it was evaluated
> from to the list of namespaces it searches while instantiating the
> template.  This is against the C++ standard.  I reported this, and many
> other similar issues, to the Visual Studio people when I was at Microsoft
> but they didn't seem that interested in fixing them.  (IIRC I was accused
> of being a "crusader" about minor issues of syntax and the C++ standard).
>
> I'm surprised the compiler crashes at that particular line of
> fstext-utils.h, I had a look and there is nothing particularly complicated
> going on there.  If someone can work out a change that will fix that issue
> I'm open to checking it in, but I'm not sure that I want to personally
> figure it out.
> Dan
>
>
>
> NB: I'm extremely annoyed ATMd m, so I'm sending it as it is, hopefully
>> someone will continue or give me hint, but at this stage it seems that
>> VS2013 cannot be used to compile Kaldi
>> The main reason is the interaction between openfst and kaldi.
>> I tried both OpenFSTWin versions --1.3.1 and 1.4.1
>> Status:
>> During compilation with OpenFSTWin 1.3.1 I was able to compile around 550
>> binaries targets out of approx 600 hundred. There were to minor fixes
>> needed (including <algorithm> where std::min and std::max were used). The
>> major problem looks like to be the way how VS2013 resolves type definition
>> -- there is openfst uint64 (and similar) and there is kaldi::uint64 (and
>> similar). VS2013 however is not able to resolve the correct type -- I get
>> bunch of erros
>>
>> error C2872: 'int32' : ambiguous symbol
>>
>> (Note: these errors can be fixed by using the :: operator, but it's not
>> probably something which would find it's way to kaldi :)
>>
>> Compiling with OpenFST 1.4.1 is even worse -- even that the ambiguity is
>> not fixed in openFST but the VS compiler manages to crash:
>>
>> 1>..\..\..\src\fstext/fstext-utils-inl.h(447): fatal error C1001: An
>> internal error has occurred in the compiler.
>> 1>  (compiler file 'msc1.cpp', line 1325)
>> 1>   To work around this problem, try simplifying or changing the program
>> near the locations listed above.
>> 1>  Please choose the Technical Support command on the Visual C++
>> 1>   Help menu, or open the Technical Support help file for more
>> information
>>
>> BTW -- it's always the fstext-utils-inl.h at the same line, of someone
>> would feel adventurous enough to figure that out. OpenFST 1.4.1 needs
>> C++/11 so I wouldn't even bother with older compilers. :)
>> In the end, I managed to compile around 130 binaries (programs) out of
>> ~600 which the kaldi VS solution has.
>>
>> BTW2: I gave it a shot and tried VS 2015 Beta and it crashes also (on the
>> same file and line)
>> y.
>>
>>
>> PS: I think I was able to get it compile last year with VS 2010
>>
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Kaldi-developers mailing list
>> Kal...@li...
>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers
>>
>>
>