How to run pocketsphinx from Windows CMD - windows

I am currently following the tutorial on cmusphinx.sourceforge.net to install pocketsphinx for Windows. Admittedly I only have experience in C#, and I'm not at all familiar with DOS commands.
My problem: When I try to run pocketsphinx_continuous, either through command prompt or by clicking on the icon, a DOS window pops up, quickly scrolls through a bunch of text, then closes before I can read anything on it. I'm not sure what to do.
My system: Windows 7 64-bit
What I've done:
I downloaded off the CMU sourceforge website the following: sphinxbase-5prealpha, pocketsphinx-5prealpha.
I unpacked both folders onto my desktop.
I went into the sphinxbase folder, opened sphinxbase.sln in Visual Studio 2012, then built the project.
I then went into the pocketsphinx folder, opened pocketsphinx.sln in Visual Studio 2012, and built the project.
I copied sphinxbase.dll from sphinxbase/bin/Release/Win32 and pasted it into pocketsphinx/bin
I tried clicking on pocketsphinx_continuous.exe. I get the problem.
I tried running in cmd C:\Users\*my name*\Desktop\pocketsphinx\bin\Release\Win32\pocketsphinx_continuous.exe -inmic yes -hmm model\en-us\en-us -lm model\en-us\en-us.lm.bin -dict model\en-us\cmudict-en-us.dict. Same problem.
I tried putting sphinxbase.dll in pocketsphinx/bin/Release/Win32. Same problem.
I tried doing all this for the files in pocketsphinx/bin/Release/x64
I tried doing all this for the files in pocketsphinx/bin/Debug/Win32(or x64)
I also tried building the projects in Visual Studio 2015, same problem.
I'm hoping I'm just making some blatant mistake, so any help would be greatly appreciated.

Related

MSVCP120.dll missing

I compiled and linked an executable file in VS2013, and then tried to run that exe on another computer.
I get this error on the other computer:
I read on this problem, and I saw I need to download VS2013 on the other computer to be able to execute this file.
But what is the point in exe file if I need to download a VS2013 on any computer I want to run it on?
Is there any normal way to execute it through the visual without go through this problem?
The MSVCP120.dll is part of the Visual C++ 2013 Redistributable package. Download and install it on the other PCs to get the program working or link the required lib via static linking.

Opening visual studio solution from a linux drive

I just upgraded from Win7 to Win10 and I noticed the following change, that I don't explain for now.
I used to checkout my source code on in a mounted linux drive (\myremote\myaccount\ as X:)
before I was able to open visual studio 2008 solution (.sln file) and build but since the upgrade to Win10, devenv fails when I double click on a sln, saying that:
The following files were specified on the command line:
X:\blahblah\myproject\myproject.sln
These files could not be found and will not be loaded
but I can open and save that sln file using a text editor.
Note that my devenv run as Administrator.
Any idea ?

How can I know tesseract has been set up successfully

I set up my tesseract 3.01 in visual studio 2008 according to http://code.google.com/p/tesseract-ocr/wiki/ReadMePre3
No errors report in compilication.
Then a console command window saying clustering flash by, then disappear.
If I have successfully installed it, where should I put tesseract examples? Is it Ok to put them under the vs2008 folder?
Can anyone send me an example?
After checking out the complete source from Tesseract SVN repositoty, open tesseract solution from vs2008 folder, select LIB-Release configuration, and build. The .exe output files can be found in vs2008\LIB_Release folder. You can move them to the parent folder of vs2008, where there are some sample images and tessdata, open a command prompt, and run your test from there.
tesseract phototest.tif out

Generating DLLs from an MC file?

I am taking over a bit of a legacy project, and having issues getting it to install in Windows 7.
The project is coded in VB, and our IDE for it is Visual Studio 2005 with VSS (fun I know). It was originally created for XP. The original dev is around to coordinate with, but is off the maintaince team for this project, and admits that the code is quite poorly formatted and commented it was his first large project.
The project runs fine when I generate a debug or release build in Visual Studio 2005, and I can run it on the Windows 7 machine that built it just fine. However, the MSI that I generate to install with fails when run on Windows 7.
It looks to be an issue where the DLLs that are packaged with the project are not correct for Windows 7, but they were generated via an MC file. I have the source MC files, so attempted to use MS's mc.exe tool and its counterparts to create the dll, but am not seeing any output.
The only walkthroughs I have seen on using MC files are not terribly helpful: mc_tutorial
MS mc.exe page
Could someone else walk me through what steps are nessary, or point me toward some more helpful resources?
An actual high quality man page for mc.exe would be quite nice, instead of the rather limited MS documenation, but maybe I am spoiled these days.
look for mc.exe in you machine (mc.exe is part of windows sdk usually located at C:\Program Files (x86)\Windows Kits\10\bin\10.0..\x64\mc.exe).
in windows command prompt run : "C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64\mc.exe" -U sample.mc
after above command run: "C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64\rc.exe" -r sample.rc
above command will generate header in your sample.mc file location.
run this command to generate dlls: link -dll -noentry -out:sample.dll sample.res

QtWebKit for Qt Visual Studio Add-in

I want to learn how to use QtWebKit by creating a simple project, but I can't even install it. I found some tutorials like this, but it's for the standard Qt package. I am using for another project the Visual Studio Qt Add-in, so I don't want to uninstall it.
I found some WebKit source code in Qt-VS, but I don't know what to do with it. It does not contain any Perl script so the tutorial above is not good for it, but it does contain some makefiles. Or should I download the QtWebKit package separately, and follow the tutorial above? Will it generate compatible libraries? (I could not find any Qt command prompt, and the tutorial says the VS command prompt must be compatible. How do I know it?) Also, where should I move the binaries generated, so the project made with the built-in Qt template in Visual Studio to be able to find these new files?
Sorry for these lame questions, but I get lost really fast when it comes to building stuff from source and not given in binary form.
I would appreciate any feedback or link to stuff
EDIT:
The only thing I could pull of is to install another copy of Qt, the normal one, and use it for the WebKit project changing the Qt environment variable value each time I'm switching the project, but that would be the lamest thing ever.
Download the Qt 4.7.3 source code:
http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.7.3.zip
Unzip and copy to a convenient location.
Open a Visual Studio 2010 command prompt.
You may need to run the command prompt as administrator. To do this, go to Start Menu > All Programs > Microsoft Visual Studio 2010 > Visual Studio Tools, right-click on Visual Studio Command Prompt (2010) and select Run as administrator.
To make a 64-bit build, select Visual Studio x64 Win64 Command Prompt (2010) instead.
Change the working directory to the Qt top folder.
Run the commands:
configure.exe -platform win32-msvc2010
nmake
Wait an hour.
This will build Qt, with all components, including QtWebKit.
Does this answer your question?
user763305's steps will work with these additions:
You need to install Perl. I used "ActiveState Perl"
You need to install WinFlex and WinBison. For some reason the QT script refers to the flex as "win_flex" but tries to find an executable called "bison.exe." I renamed "win_bison" to "bison.exe" and it worked.
I was also able to configure it successfully and build for msvc2012
configure.exe -platform win32-msvc2012
nmake
And it didn't take a few hours on my machine. Just about 55 minutes.

Resources