|
From: Daniel P. <dp...@gm...> - 2015-05-06 21:18:56
|
Apparently in Windows 10 they are going to support llvm as an option for compilation in Visual Studio. So that will fix some things. But who knows if they will break other things. Dan On Wed, May 6, 2015 at 2:15 PM, Jan Trmal <jt...@gm...> wrote: > 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. > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > |