Summary: | building with openbabel 3.0 not supported | ||
---|---|---|---|
Product: | [Applications] kalzium | Reporter: | Rik Mills <rikmills> |
Component: | general | Assignee: | Kalzium Developers <kalzium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | arojas, jscott, yuri |
Priority: | NOR | ||
Version: | 19.12 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://github.com/openbabel/openbabel/issues/2148 | ||
Latest Commit: | 2b9ebd854d85fa1e092c766e149e16ac18019496 | Version Fixed In: | 21.04.0 |
Description
Rik Mills
2020-01-28 11:10:08 UTC
This blocks introduction of the molecular editor into Debian, but I hope it'll be possible to enable building it soon: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951674 Patch available at https://git.archlinux.org/svntogit/packages.git/tree/trunk/kalzium-openbabel3.patch?h=packages/kalzium Waiting for 3.0.1 to upstream it, because the cmake files are utterly broken in 3.0.0 so you need to pass all cmake variables manually Builds with cmake -DOPENBABEL2_INCLUDE_DIR=/usr/include/openbabel3 \ -DOPENBABEL2_LIBRARIES=/usr/lib/libopenbabel.so \ -DOPENBABEL2_VERSION_MET=TRUE Upstream has given no indication of planning to make a release soon, so I've filed a bug to bring the CMake issues to their attention. (In reply to John Scott from comment #5) > Upstream has given no indication of planning to make a release soon, so I've > filed a bug to bring the CMake issues to their attention. Upstream is now certain that they will release 3.0.1 soon, which will switch to being able to use FindOpenBabel3 and fix many other issues. 3.1 is release, I've submitted my patch for review https://phabricator.kde.org/D29482 (In reply to Antonio Rojas from comment #7) > 3.1 is release, I've submitted my patch for review > > https://phabricator.kde.org/D29482 Awesome! OpenBabel 3.1.1 is making its way into Debian Unstable shortly, so when the dust settles it'll be easy to add your patch and get this enabled *** Bug 431522 has been marked as a duplicate of this bug. *** |