-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Major ABI break in 7.1.1 #6144
Comments
About map files, new entries may be added for new symbols (symbol versioning), but unchanged symbol have to stay in previous entry. Of course ABI break are possible, but in such case, please bump all soname (MagickCore, MagickWand and Magick++) |
The enum change was required to properly support multi-spectral images. We anticipated some ABI breakage which we tried to account for by bumping the library revision. We did add a member to DrawInfo, but it was added as the last member and should not disrupt the ABI. |
To date we did not have proper support for an array of meta channels, e.g. meta channels 1-6. To add support we required that the meta channel be the last channel in the enum and additional meta-channels would follow, e.g., meta1, meta2, meta3, etc. Because of the ABI disruption, we think it is best to restore the previous enums so the ABI does not break and introduce a new enum to manage an array of meta channels. We'll commit your pull request, add a patch to refactor an array of meta channels, and issue a new release, hopefully within a day or two. Thanks for your assistance with this issue. |
ImageMagick version
7.1.1-0
Operating system
Linux
Operating system, version and so on
Fedora
Description
In 6b2ae4e
This is a major ABI break as linker consider everything as new symbols.
Notice: in RPM packaging, such thing is track
Also change in enums (pixel.h) is a ABI breakage, as value defined at buildtime may change at runtime
IMHO, such breaking changes have no value...
DrawInfo struct also have change (haven't dig a lot to see if this may break things, allocation seems done in the library, not in the user app)
Steps to Reproduce
Images
No response
The text was updated successfully, but these errors were encountered: