-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build ngram and other extensions #34
Comments
Sorry, I never heard of "vs.net 201". What are you talking about? |
But yeah, we're not compiling ngram extensions yet. You can use cmake though, it compiles everything the original Makefiles do. |
If i compile extensions with cmake, will binaries be compatible with nmake? Trying to make alphacep/vosk work, gettin` the same error stack |
@LuggerMan, depends on the compiler. CMake is only a meta-builder, the choice of the toolchain is yours. Looks like some source file where these symbols are defined is not compiled. It's possible that a file is compiled, but its .o file is discarded by the linker, since it does not have referenced symbols, essentially like this problem: #36 (comment). FWIW, it may happen only with static linking; can you try DLL build? It it goes through, that's a hint. Unfortunately, I'm out of free cycles now to look into this. Will appreciate it if you diagnose the issue deeper. |
When I compile some other projects using fst with vs.net 201, got the following errors. Looks like it needs the ngram extension, please advise how to build it in vs.net with extension, very appreciated it!
The text was updated successfully, but these errors were encountered: