-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Taglib 2.0 compatibility? #127
Comments
So I attempted to regenerate swig headers with taglib 2.0, and it seems that more workarounds are needed to make swig work with taglib 2.0 as they bumped to C++17. |
Archlinux workaround, install taglib1 from AUR and do |
The taglib1 package has been moved to official repos and it's now installed to a different directory. One can run |
Thanks for raising. I haven't looked at the breaking changes yet. Maybe we can release a 2.0.0 that requires taglib 2.0, and if necessary release 1.x versions that still work with taglib 1.0. @jacobvosmaer what do you think? |
@robinst I was thinking the same thing. It seems like a lot of work and I wonder how we can break it down into manageable pieces. Perhaps by doing one format at a time? |
Yeah. I think the first step is going to be to get the CI build set up to use taglib 2. I've started that here: Note that it targets a new branch, |
Taglib has released their 2.0 version removing a few deprecated funtions that taglib-ruby seems to use.
Building taglib-ruby with taglib 2.0 fails with
Build logs
Edit: I didn't regenerate swig headers when building, I guess only the usages of
ByteVector::isNull()
andByteVector::null
and theirString
counterparts are real issues :)The text was updated successfully, but these errors were encountered: