Changes between Initial Version and Version 8 of Ticket #52479
- Timestamp:
- Oct 1, 2016, 6:58:40 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #52479
-
Property
Priority
changed from
High
toNormal
-
Property
Priority
changed from
-
Ticket #52479 – Description
initial v8 5 5 - port:kdepimlibs4 installs its own gpgme++ libraries and headers; unmodified those go into ${prefix}/include/gpgme++ and thus clash with the ones from port:gpgme 6 6 7 - KDE actually maintains its own C++ wrappers (fork or original I don't know). It seems that (very recent) KF5 code can co-exist with the headers from port:gpgme, but the KDE4 code that uses these C++ wrappers is now old and mostly unmaintained. It is unlikely that it will build and run against the 1.7.0 gpgme++ wrappers without significant modification of the build system and code (see https://trac.macports.org/ticket/52342 and https://trac.macports.org/ticket/52470). The 1.7.0 gpgme C libraries are fine, though.7 - KDE actually maintains its own C++ wrappers (fork or original I don't know). It seems that (very recent) KF5 code can co-exist with the headers from port:gpgme, but the KDE4 code that uses these C++ wrappers is now old and mostly unmaintained. It is unlikely that it will build and run against the 1.7.0 gpgme++ wrappers without significant modification of the build system and code (see #52342 and #52470). The 1.7.0 gpgme C libraries are fine, though. 8 8 9 9 The library binaries from port:kdepimlibs4 and port:gpgpme do not clash, so the main issue at hand is to avoid headerfile confusion where a gpgme++ header is included from port:gpgme when one from port:kdepimlibs4 is required, or vice versa.