https://bugs.kde.org/show_bug.cgi?id=369014
--- Comment #18 from Ryokun <renaudpi...@free.fr> --- Hello, I've been trying to compile Krita for 2 days now and after a lot of Terminal windows / dependancy installations / errors (Homebrew saved my life), I've finally been able to get an executable that works, doesn't crash at startup AND can be debugged in xCode with breakpoints (I'm an Objective-C developer so it makes much more sense to me than QT Creator). Unfortunately (for me), after all this work, when I tried to replicate the export bug... well... it didn't seem to bug anymore :) Maybe the redesigning of the export window you were talking about earlier got rid of the problem... I even tried by launching the version I compiled without debugging (directly from the Finder) in case the debugger would slow down the threads and wouldn't trigger the bug, but all worked just fine (I tried at least 15 times in a row). Just for fun after that I tried again the current release (3.1) and I had the problem almost instantly when I saved a file as PNG. So it seems that this bug has been corrected. But I will stress out that my compilation was not really orthodox: I had to compile Krita a second time in another folder exclusively with the Terminal. After the commands 'make' and 'make install', I did copy the 'etc', 'lib' and 'share' folders in the parent folder of my xCode compilation. Otherwise Krita wouldn't find the plugins and would reach a QFatal() at startup. Now it works great but I noticed that the structure is different in the packaged version (folder Frameworks, Resources/plugins, ...). I tried to copy the folders in the package of the current release (3.1), but it would crash at startup. So all in all, I think this bug might be corrected, but I really think it should be confirmed with a packaged version (sorry, I hadn't be able to do that, I still got errors for this one). Sorry for the long message (and all that to say that the bug appears to be corrected ;)). It was difficult to compile and I had to put a lot of energy in it but it was worth it: if I find another bug I will be able to put a breakpoint in xCode to see what's wrong ;) -- You are receiving this mail because: You are watching all bug changes.
