-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[DO NOT MERGE] Support openfst 1.8.2 #4829
Conversation
I do not think there was any particular reason fo removing (though the same was done in #4716). kaldi uses int32 (without I think that the intergration will be done version-by-version and we will be able to discuss the changes in the detailed PRs. |
thanks, makes sense.
yeah, sometimes the numbering vs changes was/is pretty wild in the 1.8.x
versions
y.
…On Thu, Feb 23, 2023 at 1:36 PM Yuriy Chernyshov ***@***.***> wrote:
I do not think there was any particular reason fo removing (though the
same was done in #4716 <#4716>).
kaldi uses int32 (without _t) suffix from openfst, but openfst removed
these aliases in 1.8.2 (I have no idea why this was done in a version
changing patch number only).
I think that the intergration will be done version-by-version and we will
be able to discuss the changes in the detailed PRs.
—
Reply to this email directly, view it on GitHub
<#4829 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACUKYX7E73T5GZNNQEHNDVDWY6U2JANCNFSM6AAAAAAVF7GKME>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I suppose we should leave this a few days as is, just to gather inputs from other people... @danpovey any opinion from you? |
My only comment is that I'm not a big fan of polluting the global namespace with int32, etc. It can cause downstream pain for those who use kaldi as a library. |
Is there demand for the latest version of OpenFST, or a concrete reason to upgrade? |
Just for cross-reference purposes, @mmcauliffe has a PR against this PR that could hopefully be considered here. |
So migrating to OpenFst 1.8.2 makes it a lot easier for us to get shared libraries working for Windows, and we additionally don't have to ship OpenFst 1.7.X libraries inside the kaldi package. I have everything building successfully on conda-forge here: conda-forge/kaldi-feedstock#38, but it'd be ideal to have these changes upstream. |
ping to keep it open, although we probably won't merge any time soon |
Superseding: #4716 |
Dan, just slap the label
stale-exclude
|
We merged the updated version #4716 but thank you so much for providing this POC |
yeah, apologies, I need more coffee :) |
This is a demonstration PR requested by @jtrmal in #4716.
There are only code changes, though we also have some CMakeLists changes needed to build kaldi via nixpkgs.