When I compile pocketsphinx_continuous in VS2008 as indicated in the README
file in pocketsphinx, I get six linking errors:
Linking...
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_free
referenced in function _main
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_init
referenced in function _main
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_get_hyp
referenced in function _utterance_loop
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_end_utt
referenced in function _utterance_loop
continuous.obj : error LNK2019: unresolved external symbol
__imp__ps_process_raw referenced in function _utterance_loop
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_start_utt
referenced in function _utterance_loop
....\bin\Debug\pocketsphinx_continuous.exe : fatal error LNK1120: 6
unresolved externals
What could be the problem.
Pankaj
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks nshmyrev for responding.
I am compiling pocketsphinx 0.6 and sphinxbase 0.6. Both of them get compiled
without any errors. I get the errors only while compiling the demos given in
win32 folder. I am following the instructions as given in the README file. The
README file instructs to minimally compile pocketsphinx_continuous.
Regards
Pankaj
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, there is a bug in released version and it doesn't build. We'll try to fix
shortly.
To build this app yourself do the following:
In pocketsphinx_continuous properties in input add the folder containing
pocketsphinx.lib to the list of additional library directories. It's in
Linker->General. In my case you need to add C:/bin/Debug since
pocketsphinx.lib is created there. In Linker->Input add pocketsphinx.lib to
sphinxbase.lib and winnt.lib. After that project should build fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I compile pocketsphinx_continuous in VS2008 as indicated in the README
file in pocketsphinx, I get six linking errors:
Linking...
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_free
referenced in function _main
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_init
referenced in function _main
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_get_hyp
referenced in function _utterance_loop
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_end_utt
referenced in function _utterance_loop
continuous.obj : error LNK2019: unresolved external symbol
__imp__ps_process_raw referenced in function _utterance_loop
continuous.obj : error LNK2019: unresolved external symbol __imp__ps_start_utt
referenced in function _utterance_loop
....\bin\Debug\pocketsphinx_continuous.exe : fatal error LNK1120: 6
unresolved externals
What could be the problem.
Pankaj
When you report about compilation problems please learn to provide version of
the package you are trying to compile.
As for the linking issue, you need to build pocketsphinx project first, only
then pocketsphinx_continuous.
Thanks nshmyrev for responding.
I am compiling pocketsphinx 0.6 and sphinxbase 0.6. Both of them get compiled
without any errors. I get the errors only while compiling the demos given in
win32 folder. I am following the instructions as given in the README file. The
README file instructs to minimally compile pocketsphinx_continuous.
Regards
Pankaj
Ok, there is a bug in released version and it doesn't build. We'll try to fix
shortly.
To build this app yourself do the following:
In pocketsphinx_continuous properties in input add the folder containing
pocketsphinx.lib to the list of additional library directories. It's in
Linker->General. In my case you need to add C:/bin/Debug since
pocketsphinx.lib is created there. In Linker->Input add pocketsphinx.lib to
sphinxbase.lib and winnt.lib. After that project should build fine.
Hi
This issue was fixed in trunk. The fix will appear in nightly build tomorrow
and will be availalbe in the next release.