Hi all users,
Today, i add some guards while cross-compilation of current digiKam code for Windows. Typically, there are some options that we can enable to prevent memory dysfunction under Windows. It's already proposed with Microsoft compiler and i just discovered through the Krita project that options are also available with MinGW that we use to compile the Windows version under Linux. To i activated all the guard for the 32 and 64 bits installers. Note that i cannot patch whole Qt5 and KF5 libraries. It too much complicated and require more work to do in background. I also add the DrMinGW plugin in the windows installer : This one permit to catch the debug trace in case of internal dyfunction, in a similar way than KDE crash handler work. At least, users can provide a backrace of crash without to install a debug environnement for Windows and try to reproduce the problem. I played with the installer 64 bits just recompiled today here : I scanned a large collection, scanned face, recomputed all similarity finger-prints, performs complex searches, run BQM and editor. No crash. It's just a start. I remember to crash DK very quickly under Windows just using the faces management tool. I cannot test all use cases. So my question is : do you see a stability improvements with the Windows installers published today. When i said stability, i want mean less violent application shutdowns. Thanks in advance for your feeback. Best Gilles Caulier |
Hi Gilles
Good news, will test it. just would like to know when the problem I reported on DK6.0 will be fixed: https://bugs.kde.org/show_bug.cgi?id=397972 this is from my point of view a regression compare to DK5.9, as I cannot wait hours before the completion of the flick export ( thanks to the performance of my network :-( ) I'm also wondering if I will be able to go back to DK5.9. I did it with the early beta version of DK6 but also understood this wasn't recommended because of modification of DB (new DB for similarity that I'm not using for the time being) regards frederic Le 28/08/2018 à 17:11, Gilles Caulier a écrit : > Hi all users, > > Today, i add some guards while cross-compilation of current digiKam > code for Windows. > > Typically, there are some options that we can enable to prevent memory > dysfunction under Windows. It's already proposed with Microsoft > compiler and i just discovered through the Krita project that options > are also available with MinGW that we use to compile the Windows > version under Linux. > > To i activated all the guard for the 32 and 64 bits installers. > > Note that i cannot patch whole Qt5 and KF5 libraries. It too much > complicated and require more work to do in background. > > I also add the DrMinGW plugin in the windows installer : > > https://github.com/jrfonseca/drmingw > > This one permit to catch the debug trace in case of internal > dyfunction, in a similar way than KDE crash handler work. At least, > users can provide a backrace of crash without to install a debug > environnement for Windows and try to reproduce the problem. > > I played with the installer 64 bits just recompiled today here : > > https://files.kde.org/digikam/ > > I scanned a large collection, scanned face, recomputed all similarity > finger-prints, performs complex searches, run BQM and editor. No crash. > > It's just a start. I remember to crash DK very quickly under Windows > just using the faces management tool. > > I cannot test all use cases. So my question is : do you see a > stability improvements with the Windows installers published today. > When i said stability, i want mean less violent application shutdowns. > > Thanks in advance for your feeback. > > Best > > Gilles Caulier |
2018-09-02 9:24 GMT+02:00 frederic chaume <[hidden email]>: Hi Gilles I will working on this next week. I hope to complete the job for next week end. I'm also wondering if I will be able to go back to DK5.9. I did it with the early beta version of DK6 but also understood this wasn't recommended because of modification of DB (new DB for similarity that I'm not using for the time being) If you have a DB backup done before to test 6.0.0, yes, no problem. Else, 6.0.0 DB and 5.9.0 will not be fully compatible. Trying to run 5.9.0 with a DB from 6.0.0 will introduce some dysfunctions. Gilles Caulier |
Le 02/09/2018 à 12:24, Gilles Caulier a
écrit :
thanks once you will have a version available, I will test it I have made effectively a backup, but didn't use it when switching between version 5.9 and 6.0 for the time being. I didn't notice any error so far but as said I'm not using similarity. but I will follow your advice and will reuse the 5.9 DB when going back to previous version
|
Maik has already make a patch with a generic class to create webservice tool instances in a wrapper dedicated to check if tool have already call previously an restore it as well. The tools will run in background. Flickr export is the first one to be patched : https://cgit.kde.org/digikam.git/commit/?id=c9033851a8fce90935bb746d5a0f70ef5ec0c9b0 Another point that we talk in French previously, and where i totally agree : the entry menu to change application language has nothing to do in Help main menu by in the Settings menu. You are not alone to report this problem in the past. I take a look how this behavior is implemented in KXmlGui KF5 framework from KDE and the bad new is that i cannot re-route the menu action in client application. A lots of stuff are hard coded in private in the framework component. So the only solution is to create a bugzilla file in framework-kxmlgui section. The contents must be generic as this framework is common to all KDE applications. Run Dolphin, Konsole, etc : the menu entry is in the Help section everywhere. The list of current bugzilla files are there : Gilles 2018-09-02 18:32 GMT+02:00 frederic chaume <[hidden email]>:
|
Hi Gilles yes, thanks to Maik, I saw the commit messages in the ticket. let me know when the pakage will be ready for test:-) I have created the following ticket :
https://bugs.kde.org/show_bug.cgi?id=398252 regards Frederic Le 02/09/2018 à 18:45, Gilles Caulier a
écrit :
|
Frederic, I broken something in Windows build workflow, trying to include a cross-compiled version of libgphoto2. It's fixed now, but without libgphoto2. I also reported a broken package in MXE project. The Windows builds will be pushed at usual place this evening if all is fine, not before, i'm not in my office today. Best Gilles Caulier 2018-09-04 18:20 GMT+02:00 frederic chaume <[hidden email]>:
|
Frederic, All he bundles are now updated to at usual place with current code from git/master. Gilles 2018-09-11 7:49 GMT+02:00 Gilles Caulier <[hidden email]>:
|
Bonjour Gilles Super Je suis en vacances, je teste ça la semaine prochaine Frédéric Le sam. 15 sept. 2018 à 15:37, Gilles Caulier <[hidden email]> a écrit :
|
Any feedback here ? Best Gilles Caulier 2018-09-15 18:03 GMT+02:00 Frederic Chaume <[hidden email]>:
|
In reply to this post by Gilles Caulier-4
Hi Gilles just downloaded the last digiKam-6.0.0-beta1-20180916T150303-Win64.exe Access to the album is now possible during export. (tested from album view and editor), thanks a lot.
some other feedback
will continue the test with this new version.
thanks a lot for your help
Le 15/09/2018 à 15:36, Gilles Caulier a
écrit :
|
Free forum by Nabble | Edit this page |