https://bugs.kde.org/show_bug.cgi?id=375385
Wolfgang Rohdewald <wolfg...@rohdewald.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Version Fixed In| |master
Latest Commit| |5a2610e5e6a105386e4ee47615a
| |e94d14aa86fad
Resolution|WAITINGFORINFO |FIXED
--- Comment #5 from Wolfgang Rohdewald <wolfg...@rohdewald.de> ---
Python kf5 bindings are heavily being worked on - see kde-bindings mailing
list, but not yet ready. Plus - I want kajongg to run on windows too - and I do
not believe Python kf5 bindings will ever run on windows. So - when kf5
bindings are available, I will use them but I will always need a python-only
alternative anyway.
kajongg always used the normal *.mo gettext translation system like most KDE
program do, I see no advantage in changing that to the Qt system.
I know kf5-config is deprecated but I wanted to see its source code.
It seems like the paths in kf5-config are hard coded at compile time.
So that is what current master kajongg now does: cmake creates a python script
defining those paths. If this does not work for you, please tell me what cmake
writes into kajongg/kdepaths.py for you.
I would not really like to use qtpaths/QStandardDirs because I am quite sure it
is possible to compile KDE into a separate user installed directory using the
system-based Qt5 packages. Qt5 would then be in /usr/share but KDE would not.
--
You are receiving this mail because:
You are watching all bug changes.
