Summary: | Python plugins are unusable | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Timothy Edmund Crosley <timothy.crosley> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | major | CC: | jr, lbeltrame |
Priority: | NOR | ||
Version: | 3.11.1 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Timothy Edmund Crosley
2013-09-30 12:24:25 UTC
Jonathan, can you take care of this? According to the reporter, this is a Kubuntu issue. https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1233215 a sip mystery :( Fixed it in our package by setting the path manually to the python library -DPYTHON_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython2.7.so.1 (it automatically picked up -DPYTHON_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython2.7.so) I think this is still an upstream issue though, we shouldn't have to set it manually, could be something up in Sip or how Kate uses the CMake variables. Can I just say you guys are awesome? I've used KDE with various distributions for years (and with Kubuntu for the last ~2) but never reported a bug until now. I am amazed at how quickly it was acknowledged and came to some form of resolution. Thank you! PYTHON_LIBRARY is set to be the same as PYTHON_LIBRARIES (this to keep SC) in kdelibs's FindPythonLibrary.cmake. Therefore, if there is an issue, it lies within cmake's FindPythonLibs.cmake, which is the one setting PYTHON_LIBRARIES. (Notice: I don't have a Kate checkout to look at how it's used for Pate). Yes the other culprit might be Ubuntu/Debian patches to FindPythonLibrary.cmake to support our multiarch layout for libraries The Kate Pate Python host uses macro_optional_find_package(PythonLibrary) FindPythonLibrary.cmake is shipped with kdelibs it seems. The Kate Pate Python host then links to ${PYTHON_LIBRARY}. If there is anything wrong with this, please let us know. @Timothy: The bug is resolved so quickly mostly because of your well-described report, most importantly you provided the solution. So thanks for your contribution here :-) |