Debug Krita 4.0.0.xxxx beta python loading
Metallicow opened this issue · 1 comments
Summary of irc discussion to fix python problems with krita.
Ref issue: https://forum.kde.org/viewtopic.php?f=281&t=150613
windragon
Metallicow: https://bugs.kde.org/show_bug.cgi?id=388848
Metallicow
@windragon Thanks. Downloading the nightly build now. Will test in a few..
Metallicow
@windragon boud I just got the nightly snapshot downloaded and I still do not see the option in 'Configure Krita...'...? Do I still need the windows update/patch or do I need to do a reset of app data or what? I'm guessing the nightly is 'portable'?
windragon
Metallicow: check what the debugview output has to offer
Metallicow
@windragon boud https://thepasteb.in/p/DRhjA8lnYL3Sy
windragon
Metallicow: try to copy python/vcruntimexx.dll to bin/ and see if it works
if it does, then I guess I'll need to fix that... and properly
Metallicow
@windragon Is there a doc anywhere that states where these builds are coming from or built with? My best experience is that windows builds are done on windows, not cross-compiled for example...
Metallicow
@windragon boud One visual thing I do note about the windows nightly build is that the list widget position of 'Color Selector Settings' and 'G'Mic-Qt-Integration' seemed to swap places at some point. Upon restart with the nightly 'G'Mic-Qt-Integration' is now at the bottom of the list widget... Coming from a GUI dev myself, this is not regular behavior. If I am right the 'Python Plugin Manager' should also be a item in the widget list. ...so maybe start looking there.
windragon
Metallicow: the nightly build uses the same workflow as previous nightly builds and releases since 3.0, it's not cross-compiled
Metallicow: one thing you can try is to use dependency walker's profiling function to check which DLL failed to load
Metallicow
@windragon I'm not the compiled.exe debugging type so maybe this will help...?
windragon
Metallicow: you need to find kritapykrita.dll on the list and show it on the tree view
Metallicow
Ok what am I looking at here as far as a point of failure?
windragon
Metallicow: I guess when you start the profiling, enable the option "log loadlibrary function calls"