During the day I tried several times tot compile the latest svn-version. It
constantly gives errors on libkdcraw while in the make-proces. The last try was on revision 861284 and gave the next output. [...] In file included from ../libraw/libraw/libraw.h:33, from kdcrawprivate.h:32, from kdcraw.cpp:43: ../libraw/libraw/libraw_types.h:103: warning: ignoring #pragma omp firstprivate ../libraw/libraw/libraw_types.h:135: warning: ignoring #pragma omp firstprivate ../libraw/libraw/libraw_types.h:215: warning: ignoring #pragma omp firstprivate ../libraw/libraw/libraw_types.h:252: warning: ignoring #pragma omp shared kdcraw.cpp:45:22: error: kdcraw.moc: No such file or directory make[3]: *** [libkdcraw_la-kdcraw.lo] Fout 1 make[3]: Map '/home/builds/digikam-svn/libs/libkdcraw/libkdcraw' wordt verlaten make[2]: *** [all-recursive] Fout 1 make[2]: Map '/home/builds/digikam-svn/libs/libkdcraw' wordt verlaten make[1]: *** [all-recursive] Fout 1 make[1]: Map '/home/builds/digikam-svn/libs' wordt verlaten make: *** [all] Fout 2 Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Caspar,
I know this error. i working to fix it... but... Do not try to use current implementation of libkdcraw from svn. it's based on libraw (bye bye dcraw), and for KDE3 (and only KDE3), libraw crash digiKam. i'm currently working as acrazy with Alex Tutubalin from libraw team to fix it. Note that libkdcraw from trunk (KDE4) is already ported to libraw and work like a charm. so, for KDE3, please use for the moment libkdcraw 0.1.5, just released this week. this is the last version based on dcraw. Best Gilles Caulier 2008/9/15 Caspar Maessen <[hidden email]> During the day I tried several times tot compile the latest svn-version. It _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Op maandag 15 september 2008, schreef Gilles Caulier:
> Do not try to use current implementation of libkdcraw from svn. it's > based on libraw (bye bye dcraw), and for KDE3 (and only KDE3), libraw > crash digiKam. i'm currently working as acrazy with Alex Tutubalin from > libraw team to fix it. Ok. Thanks for the message. For the time being I will comment out the libs part of my download/install script. I take it that you will signal the list when the problem has been fixed. Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Ok, compilation is not broken anymore, but libraw still to crash digiKam
Please just try a fresh checkout of extragear/libs and compile to see all is fne with automake/autoconf/gcc. But do not install libkdcraw 0.1.6 for the moment. Gilles 2008/9/15 Caspar Maessen <[hidden email]> Op maandag 15 september 2008, schreef Gilles Caulier: _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Op dinsdag 16 september 2008, schreef Gilles Caulier:
> Ok, compilation is not broken anymore, but libraw still to crash digiKam Compile went well. And indeed digiKam crashes while opening a nef-file for viewing or editing. See debug trace: [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb57d56d0 (LWP 20639)] [New Thread 0xb51a7b90 (LWP 20756)] [New Thread 0xb49a6b90 (LWP 20755)] 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb5c66ffb in read () from /lib/libpthread.so.0 #2 0xb5b23443 in ?? () from /usr/lib/libxcb.so.1 #3 0x00000003 in ?? () #4 0x08062344 in ?? () #5 0x00001000 in ?? () #6 0xb5b31ff4 in ?? () from /usr/lib/libxcb.so.1 #7 0x080622b0 in ?? () #8 0x00000000 in ?? () But it does this as well for jpg's. But only in the case of a file with the jpg-extension, and while opening for preview, not for editing. The same file with an extension of .cma (I use that extension to distinguish my "proxy-file") gives no problems. [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb57ab6d0 (LWP 21740)] [New Thread 0xb517cb90 (LWP 21815)] [New Thread 0xb497bb90 (LWP 21814)] 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb586c591 in select () from /lib/libc.so.6 #2 0xb5af8165 in ?? () from /usr/lib/libxcb.so.1 #3 0x00000004 in ?? () #4 0xbfaf42fc in ?? () #5 0xbfaf427c in ?? () #6 0x00000000 in ?? () Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Caspar.
libraw compilation is now fixed in KDE3 svn branch. I think you can use it safety with digiKam. cleanup all, and recompile libkdcraw, kipi-plugins and digiKam. Let's me hear if you fell some troubles when you use digiKam... Gilles 2008/9/16 Caspar Maessen <[hidden email]> Op dinsdag 16 september 2008, schreef Gilles Caulier: _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Op dinsdag 16 september 2008, schreef Gilles Caulier:
> libraw compilation is now fixed in KDE3 svn branch. I think you can use > it safety with digiKam. cleanup all, and recompile libkdcraw, > kipi-plugins and digiKam. Let's me hear if you fell some troubles when > you use digiKam... That was quick, and a job well done. Compilation Ok, as well as viewing and editing all filetypes. The only thing is that in the settings dialog the raw decoding options are lost. There is an entry in the dialog, and a tab De... , and that's it. No further options. The batch converter on the other hand, shows a nice array of tabs and options to handle. Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2008/9/16 Caspar Maessen <[hidden email]>
hum, just fixed a little bug in libkdcraw. just checkout
Ah... not here i think, let's me try Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Op dinsdag 16 september 2008, schreef Gilles Caulier:
> hum, just fixed a little bug in libkdcraw. just checkout Again, compiled ok. > > ... the settings dialog the raw decoding options are lost > Ah... not here i think, let's me try I have no clue what can be wrong then. Something specific with my setup? Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2008/9/16 Caspar Maessen <[hidden email]>
Ah, yes, i can reproduce it now. it's a layout problem. i will fix it. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Fixed in svn
Gilles 2008/9/16 Gilles Caulier <[hidden email]>
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Op dinsdag 16 september 2008, schreef Gilles Caulier:
> Fixed in svn What a service! Thank you. Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2008/9/16 Caspar Maessen <[hidden email]>
libraw is update to 0.6.0-beta2 in svn. please update, compile and test again Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Caspar,
I will post a new entry in my blog about libraw support in digiKam, to describe a technical review. But there is some report from users that i would to see in this room about libkdcraw 0.1.6 based on libraw, especially about speed improvements: - We don't use KProcess to fork dcraw program. forking take more time than to use multithreading. - Demosaiced Raw data are taken directly in memory. It's fast. before, with dcraw, we use a pipe. It's more slow - Auto gamma adjustment in 16 bits color depth is done by main demosaicing loop from libraw. Before, it's done in digiKam Raw loader, because dcraw do not support this mode. This is want mean that we have another loop in the trash. It's faster - The same way is done for thumbnail. we recieve image data from memory without to use KProcess. It's faster. - At startup, we don't check dcraw program installed on your computer. This speed up this part a little. BUT the best is for the future ! Libraw use now openmp to parallelize demosaicing jobs !!! Can you feel it... More info here : http://openmp.org/wp/ OpenMp extension for GCC is included by default with 4.2 version of compiler... This is want mean that RAW time loading will be decreased around 30-40% (first test done here with a dual core processor). This is a major improvement for digiKam and RAW workflow. This mode is not yet enabled by default. I need to test indeep before... This way have been possible with help of Holger Berger, who have written a patch for dcraw to parallelize code. Note that this patch have never been accepted by Dave Coffin, so dcraw will continue to use a non parallelized code for a while (and same for UFRAW). If you have already tested Bibblepro, it use also a parallelized code to demosaic raw file (based on dcraw too, dixit dcraw web page). this is why this program is fast to play with RAW... This will be the same with digiKam in a near future (:=))) Gilles Caulier 2008/9/16 Gilles Caulier <[hidden email]>
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Op dinsdag 16 september 2008, schreef Gilles Caulier:
> I will post a new entry in my blog about libraw support in digiKam, to > describe a technical review. All in all, enough reasons to make the switch. And indeed there seems to be an increase in speed viewing my nefs. About editing I cannot tell, because of too little experience with converting and editing raw files with digiKam. > If you have already tested Bibblepro, it use also a parallelized code to > demosaic raw file (based on dcraw too, dixit dcraw web page). this is why > this program is fast to play with RAW... This will be the same with > digiKam in a near future (:=))) Yes, I am using BibblePro, and besides the overview of the different editiing-options, the speed is the main reason. Indeed that is something for digiKam to wish for. But you are working on it, and I am confident in the outcome. You are doing a great job! Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Gilles Caulier-4
Dnia Tuesday 16 of September 2008, Gilles Caulier napisaĆ:
> Caspar, > > I will post a new entry in my blog about libraw support in digiKam, to > describe a technical review. Really impressive. Thanks :) m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |