Hello everybody. Please pardon my ignorance but, I'm much more of a photographer than a Linux wizard...
Like many others, I've been plagued by the problem of slowwwwwwww... photo imports. Yes, I am a proud Nikon D90 owner. I understand that exiv2 was the culprit and I also know that version 2 has been developed to overcome the problem. This is good. What's not good is that I have absolutely no idea whatsoever about how to take advantage of this new file; How do I incorporate it into my version of DigiKam (1.6.0) running on Ubuntu 10.10??? If anybody can lead me through the painful process (with many noob-necessary details) I would be very appreciative. Ciao y'all. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
You want mean exiv2 0.20 or 0.21.
To use these version in digiKam, you need to recompile and install libkexiv2, the KDE/Qt interface of Exiv2 used by digiKam. After that, digiKam and kipi-plugins need to be recompiled too. If you use precompiled packages, try to update libkexiv2 as well. After go to Help/Components Info from digiKam to see which version is used in background. Gilles Caulier 2010/12/18 Hevï Guy <[hidden email]>: > Hello everybody. Please pardon my ignorance but, I'm much more of a > photographer than a Linux wizard... > > Like many others, I've been plagued by the problem of slowwwwwwww... photo > imports. Yes, I am a proud Nikon D90 owner. I understand that exiv2 was the > culprit and I also know that version 2 has been developed to overcome the > problem. This is good. What's not good is that I have absolutely no idea > whatsoever about how to take advantage of this new file; How do I > incorporate it into my version of DigiKam (1.6.0) running on Ubuntu 10.10??? > > If anybody can lead me through the painful process (with many noob-necessary > details) I would be very appreciative. > > Ciao y'all. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Salut Gilles. Thank you very much for your almost immediate response!
Yes, I used a precompiled version via http://ppa.launchpad.net/ferramroberto/digikam/ubuntu . I had no choice because the entire building-from-scratch exercise is very foreign to me. This is the second component of my very frustrating dilemma: I've no idea how to roll my own package! So, while I certainly appreciate your kind assistance thus far Gilles, what I really need is some detailed step-by-step guidance for what many in this forum would find to be a ridiculously simple thing to do. Many thanks in advance! On Sat, 2010-12-18 at 07:04 +0100, Gilles Caulier wrote: You want mean exiv2 0.20 or 0.21. To use these version in digiKam, you need to recompile and install libkexiv2, the KDE/Qt interface of Exiv2 used by digiKam. After that, digiKam and kipi-plugins need to be recompiled too. If you use precompiled packages, try to update libkexiv2 as well. After go to Help/Components Info from digiKam to see which version is used in background. Gilles Caulier 2010/12/18 Hevï Guy <[hidden email]>: > Hello everybody. Please pardon my ignorance but, I'm much more of a > photographer than a Linux wizard... > > Like many others, I've been plagued by the problem of slowwwwwwww... photo > imports. Yes, I am a proud Nikon D90 owner. I understand that exiv2 was the > culprit and I also know that version 2 has been developed to overcome the > problem. This is good. What's not good is that I have absolutely no idea > whatsoever about how to take advantage of this new file; How do I > incorporate it into my version of DigiKam (1.6.0) running on Ubuntu 10.10??? > > If anybody can lead me through the painful process (with many noob-necessary > details) I would be very appreciative. > > Ciao y'all. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Gilles Caulier-4
Somebody was very kind to provide me with detailed instructions (merci, Christian). Unfortunately, they were for a Fedora system (I'm running Maverick). I was able to find a cross-reference of Fedora vs Ubuntu commands and, I think I did fairly well. Unfortunately, I fell into a Fedora hole and can't get out now. As a result, I have no digiKam at all on my box!
I'm not embarrassed to say that I AM NOT A COMMAND LINE KINDA GUY!!! It seems that many über-techies in the Linux world treat the rest of us with utter disdain. I feel like I'm being laughed at because I'm not a member of this very elite club. I can't stress enough that I am on my knees appealing for, no, BEGGING for some detailed instructions that I can simply cut and paste to get this wonderful program working for me the way that it was intended. It amazes me that in spite of there probably being hundreds of people in the same position (needing to upgrade so that we can overcome this damn exiv2 Nikon bug), everybody must reinvent their own wheel! What's the story? Perhaps there's a reason for this but, it's simply bizarre to me. Does it give perverse pleasure to the experts when watching those who aren't members of this elite society struggling and almost drowning until they're forced to swim back to the evil Windoze shore? YES, you are gods! I'll run out and find a goat so that I can sacrifice it to you! Then, will someone PLEASE take pity on not only me but also on my fellow simple mortals and provide us with the guidance that we so desperately require? I already owe Christian a beer, there will be another one for whichever Good Samaritan will light the way. On Sat, 2010-12-18 at 07:04 +0100, Gilles Caulier wrote: You want mean exiv2 0.20 or 0.21. To use these version in digiKam, you need to recompile and install libkexiv2, the KDE/Qt interface of Exiv2 used by digiKam. After that, digiKam and kipi-plugins need to be recompiled too. If you use precompiled packages, try to update libkexiv2 as well. After go to Help/Components Info from digiKam to see which version is used in background. Gilles Caulier 2010/12/18 Hevï Guy <[hidden email]>: > Hello everybody. Please pardon my ignorance but, I'm much more of a > photographer than a Linux wizard... > > Like many others, I've been plagued by the problem of slowwwwwwww... photo > imports. Yes, I am a proud Nikon D90 owner. I understand that exiv2 was the > culprit and I also know that version 2 has been developed to overcome the > problem. This is good. What's not good is that I have absolutely no idea > whatsoever about how to take advantage of this new file; How do I > incorporate it into my version of DigiKam (1.6.0) running on Ubuntu 10.10??? > > If anybody can lead me through the painful process (with many noob-necessary > details) I would be very appreciative. > > Ciao y'all. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by J Albrecht
Hi,
I read your last message, but unfortunately I delete it by mistake, so I answer by this way. Le Sat, 18 Dec 2010 05:37:59 +0100, Hevï Guy <[hidden email]> a écrit: I understand building from source is not an easy way to update, and it's hard to wait 6 months before getting a new release with the hope the annoying bugs will be fixed. But I don't think the "compile masters" see us as annoying little guys, but they can't solve everything for us, particularly if something is not depending upon them (here the update policy of Ubuntu). So, may be you could expose your actual matter instead of just saying you have some. May be explain what you have did and what was this fedora tips... There's some hopes for Ubuntu future Update policy as Mark Shuttleworth says his will to see more dynamic update in Ubuntu for some components in the future, and not maintaining this version block for all components as actual. But for the moment it's just words. -- Nicolas Boulesteix Photographe chasseur de lueurs http://www.photonoxx.fr _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2010/12/19 Photonoxx <[hidden email]>
That was my reason to leave Ubuntu for Fedora a couple of months ago. I'm perfectly happy now, with new versions for Digikam and Scribus a few days after they get published; I'm definitely not going back to Ubuntu. My own 0.02, Marie-Noëlle -- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by J Albrecht
On 12/18/2010 05:37 AM, Hevï Guy wrote:
> Hello everybody. Please pardon my ignorance but, I'm much more of a > photographer than a Linux wizard... > If anybody can lead me through the painful process (with many > noob-necessary details) I would be very appreciative. Maybe this can be helpful to you: http://www.digikam.org/drupal/download/SvnAlongStable Michael _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Thank-you Michael. A few more Noob questions:
If I am somehow successful in getting DigiKam running by following what seems to be a complete set of instructions in your link, how would I then delete the stable version? Will it be safe to delete the development folder and contents after a successful build (I assume that the build also makes all the appropriate directories and populates the files accordingly, right?). Jörg On Sun, 2010-12-19 at 15:56 +0100, Michael G. Hansen wrote: On 12/18/2010 05:37 AM, Hevï Guy wrote: > Hello everybody. Please pardon my ignorance but, I'm much more of a > photographer than a Linux wizard... > If anybody can lead me through the painful process (with many > noob-necessary details) I would be very appreciative. Maybe this can be helpful to you: http://www.digikam.org/drupal/download/SvnAlongStable Michael _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 12/19/2010 07:50 PM, Hevï Guy wrote:
> Thank-you Michael. A few more Noob questions: > > If I am somehow successful in getting DigiKam running by following what > seems to be a complete set of instructions in your link, how would I > then delete the stable version? You would have to uninstall it using the package management tools of your distribution - for ubuntu, 'sudo apt-get remove digikam'. However, you should first remove it, otherwise your installation overwrites the files which apt-get thinks are in the package, and then they may be removed when you uninstall. > Will it be safe to delete the development folder and contents after a > successful build (I assume that the build also makes all the appropriate > directories and populates the files accordingly, right?). Once you ran 'make install', yes, you can remove the build folder. Michael _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I *hate* bothering you with such basic questions but, I've no choice. Thank you for your understanding...
The instructions that you've kindly provided to me are to install an svg package alongside the stable package. Are you now saying that I should just get rid of my stable package completely before I try to complile? On Sun, 2010-12-19 at 19:58 +0100, Michael G. Hansen wrote: On 12/19/2010 07:50 PM, Hevï Guy wrote: > Thank-you Michael. A few more Noob questions: > > If I am somehow successful in getting DigiKam running by following what > seems to be a complete set of instructions in your link, how would I > then delete the stable version? You would have to uninstall it using the package management tools of your distribution - for ubuntu, 'sudo apt-get remove digikam'. However, you should first remove it, otherwise your installation overwrites the files which apt-get thinks are in the package, and then they may be removed when you uninstall. > Will it be safe to delete the development folder and contents after a > successful build (I assume that the build also makes all the appropriate > directories and populates the files accordingly, right?). Once you ran 'make install', yes, you can remove the build folder. Michael _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Michael G. Hansen
First problem encountered...
Following the instructions given at http://www.digikam.org/drupal/download/SvnAlongStable I've been able to get as far as "Patch CMakeLists.txt to be able to build standalone. Download appended patch and place it in your development folder." I found the original CMakeLists.txt on my boat trunk/libkeeiv2/ and, I found the patch via the link: Index: CMakeLists.txt =================================================================== --- CMakeLists.txt (Revision 1117624) +++ CMakeLists.txt (Arbeitskopie) @@ -1,5 +1,20 @@ PROJECT(libkexiv2) +FIND_PACKAGE(KDE4 REQUIRED) +INCLUDE(KDE4Defaults) +INCLUDE(MacroLibrary) +INCLUDE(MacroOptionalAddSubdirectory) +INCLUDE(FindPackageHandleStandardArgs) + +ADD_DEFINITIONS (${QT_DEFINITIONS} ${QT_QTDBUS_DEFINITIONS} ${KDE4_DEFINITIONS}) +INCLUDE_DIRECTORIES (${QDBUS_INCLUDE_DIRS} ${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR} ${KDE4_INCLUDES}) + +# Preview acess was added in Exiv2 0.18 +# IMPORTANT : Several fixes done in 0.19. Set as default version when KDE 4.4 will be released +set(EXIV2_MIN_VERSION "0.18") +macro_optional_find_package(Exiv2) +macro_log_feature(EXIV2_FOUND "Exiv2" "A library to access image metadata" "http://www.exiv2.org" FALSE ${EXIV2_MIN_VERSION} "Required to build libkexiv2 and gwenview.") + # ======================================================= # Information to update before to release this library. I assume that I copy the above and paste it into CMakeLists.txt. Is this correct? Where do I append it? At the beginning? At the end? On Sun, 2010-12-19 at 19:58 +0100, Michael G. Hansen wrote: On 12/19/2010 07:50 PM, Hevï Guy wrote: > Thank-you Michael. A few more Noob questions: > > If I am somehow successful in getting DigiKam running by following what > seems to be a complete set of instructions in your link, how would I > then delete the stable version? You would have to uninstall it using the package management tools of your distribution - for ubuntu, 'sudo apt-get remove digikam'. However, you should first remove it, otherwise your installation overwrites the files which apt-get thinks are in the package, and then they may be removed when you uninstall. > Will it be safe to delete the development folder and contents after a > successful build (I assume that the build also makes all the appropriate > directories and populates the files accordingly, right?). Once you ran 'make install', yes, you can remove the build folder. Michael _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by J Albrecht
> I *hate* bothering you with such basic questions but, I've no choice. Thank
> you for your understanding... > > The instructions that you've kindly provided to me are to install an svg > package alongside the stable package. Are you now saying that I should just > get rid of my stable package completely before I try to complile? I would say that "svn alongside stable" is advanced option. But the instuctions as generally good except that You could use -DCMAKE_INSTALL_PREFIX=/usr instead of -DCMAKE_INSTALL_PREFIX=/usr/local Gert _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by J Albrecht
On 20 December 2010 06:21, Hevï Guy <[hidden email]> wrote:
> First problem encountered... > > Following the instructions given at > http://www.digikam.org/drupal/download/SvnAlongStable I've been able to get > as far as "Patch CMakeLists.txt to be able to build standalone. Download > appended patch and place it in your development folder." I found the > original CMakeLists.txt on my boat trunk/libkeeiv2/ and, I found the patch > via the link: It's given in the page, second line in scrip sample: patch < ../libkexiv2cmake.diff Gert _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
>> Following the instructions given at
>> http://www.digikam.org/drupal/download/SvnAlongStable I've been able to get >> as far as "Patch CMakeLists.txt to be able to build standalone. Download >> appended patch and place it in your development folder." I found the >> original CMakeLists.txt on my boat trunk/libkeeiv2/ and, I found the patch >> via the link: > > It's given in the page, second line in scrip sample: > > patch < ../libkexiv2cmake.diff Forgot: Perhaps You should use the sample script to get diff file also: wget http://www.digikam.org/drupal/system/files/libkexiv2cmake.diff_.txt -O ../libkexiv2cmake.diff Gert _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by J Albrecht
Well, I decided to blast through on my own. I didn't "patch" anything but rather simply cut and pasted the next line from the instructions :
# wget http://www.digikam.org/drupal/system/files/libkexiv2cmake.diff_.txt -O ../libkexiv2cmake.diff I then got as far as halfway through the digiKam build exercise. Seems like I hit a brick wall because I was told "-- Configuring incomplete, errors occurred!" It seems this is because apparently I don't have libkipi, libkexiv2 nor libkdcraw installed. Huh?? I followed the instructions precisely up to this point (a point for those who'd like to know exactly what I did, the instructions via the above link will be a guidleine). Shouldn't these libraries therefore be installed? Are the instructions lacking? Can somebody please pull me out of the quagmire? Here are the details... [hidden email]:~/trunk/digikam/build$ cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - not found. -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found. -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found. -- Found Qt-Version 4.7.0 (using /usr/bin/qmake) -- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so -- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so - found -- Looking for gethostbyname -- Looking for gethostbyname - found -- Looking for connect -- Looking for connect - found -- Looking for remove -- Looking for remove - found -- Looking for shmat -- Looking for shmat - found -- Looking for IceConnectionNumber in ICE -- Looking for IceConnectionNumber in ICE - found -- Found X11: /usr/lib/libX11.so -- Looking for include files CMAKE_HAVE_PTHREAD_H -- Looking for include files CMAKE_HAVE_PTHREAD_H - found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE -- Looking for _POSIX_TIMERS -- Looking for _POSIX_TIMERS - found -- Found Automoc4: /usr/bin/automoc4 -- Found Perl: /usr/bin/perl -- Found Phonon: /usr/include (found version "4.4.2", required is "4.3.80") -- Performing Test _OFFT_IS_64BIT -- Performing Test _OFFT_IS_64BIT - Failed -- Performing Test HAVE_FPIE_SUPPORT -- Performing Test HAVE_FPIE_SUPPORT - Success -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success -- Performing Test __KDE_HAVE_GCC_VISIBILITY -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success -- Found KDE 4.5 include dir: /usr/include -- Found KDE 4.5 library dir: /usr/lib -- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler -- Found automoc4: /usr/bin/automoc4 -- checking for module 'lcms' -- found lcms, version 1.18 -- Found lcms version 1.18, /usr/lib/liblcms.so -- Found JPEG: /usr/lib/libjpeg.so -- Found ZLIB: /usr/include -- Found PNG: /usr/lib/libpng.so -- Found TIFF: /usr/lib/libtiff.so -- Found Jasper: /usr/lib/libjasper.so -- Check Kdcraw library in local sub-folder... -- Check Kdcraw library using pkg-config... -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig -- PKGCONFIG() indicates that libkdcraw is not installed (install the package which contains libkdcraw.pc if you want to support this feature) -- Check Kexiv2 library in local sub-folder... -- Check Kexiv2 library using pkg-config... -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig -- PKGCONFIG() indicates that libkexiv2 is not installed (install the package which contains libkexiv2.pc if you want to support this feature) -- Check Kipi library in local sub-folder... -- Check Kipi library using pkg-config... -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig -- PKGCONFIG() indicates that libkipi is not installed (install the package which contains libkipi.pc if you want to support this feature) -- checking for module 'libpgf' -- package 'libpgf' not found -- Could NOT find any working clapack installation -- Identified libjpeg version: 62 -- checking for module 'libkdcraw>=1.1.0' -- package 'libkdcraw>=1.1.0' not found -- checking for module 'libkexiv2>=1.1.0' -- package 'libkexiv2>=1.1.0' not found -- Found MySQL server executable at: /usr/sbin/mysqld -- Found MySQL install_db executable at: /usr/bin/mysql_install_db -- Found gphoto2: -L/usr/lib -lgphoto2_port;-L/usr/lib -lgphoto2 -lgphoto2_port -lm -- Found KdepimLibs: /usr/lib/cmake/KdepimLibs/KdepimLibsConfig.cmake -- Found Marble: /usr/lib/libmarblewidget.so -- Can build Marble plugin: yes -- Found GLIB2: /usr/lib/libglib-2.0.so -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig -- Found LensFun: /usr/include -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig -- Performing Test HAVE_LQR_0_4 -- Performing Test HAVE_LQR_0_4 - Success -- Found Lqr-1: /usr/include/lqr-1 -- Found Soprano: /usr/include -- Found SharedDesktopOntologies: /usr/share/ontology -- Found Nepomuk: /usr/lib/libnepomuk.so -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) -- -- ---------------------------------------------------------------------------------- -- digiKam 1.8.0 dependencies results <http://www.digikam.org> -- -- Qt4 SQL module found..................... YES -- MySQL Server found....................... YES -- MySQL install_db tool found.............. YES -- libtiff library found.................... YES -- libpng library found..................... YES -- libjasper library found.................. YES -- liblcms library found.................... YES -- libkipi library found.................... NO -- CMake Error at CMakeLists.txt:86 (MESSAGE): digiKam needs libkipi. You need to install the libkipi (version >= 0.2.0) library development package. Call Stack (most recent call first): CMakeLists.txt:285 (PRINT_LIBRARY_STATUS) -- libkipi website is at http://www.digikam.org/sharedlibs -- -- libkexiv2 library found.................. NO -- CMake Error at CMakeLists.txt:86 (MESSAGE): digiKam needs libkexiv2. You need to install the libkexiv2 (version >= 1.1.0) library development package. Call Stack (most recent call first): CMakeLists.txt:286 (PRINT_LIBRARY_STATUS) -- libkexiv2 website is at http://www.digikam.org/sharedlibs -- -- libkdcraw library found.................. NO -- CMake Error at CMakeLists.txt:86 (MESSAGE): digiKam needs libkdcraw. You need to install the libkdcraw (version >= 1.1.0) library development package. Call Stack (most recent call first): CMakeLists.txt:287 (PRINT_LIBRARY_STATUS) -- libkdcraw website is at http://www.digikam.org/sharedlibs -- -- libpgf library found..................... NO (optional - internal version used instead) -- libclapack library found................. NO (optional - internal version used instead) -- libgphoto2 library found................. YES (optional) -- libkdepimlibs library found.............. YES (optional) -- libmarblewidget library found............ YES (optional) -- Can build Marble plugin.................. YES (optional) -- Nepomuk libraries found.................. YES (optional) -- libglib2 library found................... YES (optional) -- liblqr-1 library found................... YES (optional) -- liblensfun library found................. YES (optional) -- Doxygen found............................ NO (optional) -- -- You will not be able to to generate the API documentation. -- This does not affect building digiKam in any way. -- CMake Error at CMakeLists.txt:399 (MESSAGE): digiKam will be compiled................. NO (Look README file for more details about dependencies) -- Configuring incomplete, errors occurred! [hidden email]:~/trunk/digikam/build$ ^C heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ On Sun, 2010-12-19 at 22:21 -0600, Hevï Guy wrote: First problem encountered... _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hi.
Seems like something did not got installed. I assume You did successfully compile and install exiv2? I mixed a script for You based on http://www.digikam.org/drupal/download/KDE4 I would say You could use -DCMAKE_INSTALL_PREFIX=/usr instead of -DCMAKE_INSTALL_PREFIX=/usr/local (the -DCMAKE_INSTALL_PREFIX=/usr would overwrite the "stable" version of digikam, so "not along stable") svn co -N svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegraphics cd kdegraphics svn up libs svn up cmake cd .. svn co -N svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics cd graphics svn up digikam svn up kipi-plugins svn up cmake cd ../kdegraphics mkdir build cd build cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. make sudo make install cd ../../graphics mkdir build cd build cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. make sudo make install On 20 December 2010 14:46, Hevï Guy <[hidden email]> wrote: > Well, I decided to blast through on my own. I didn't "patch" anything but > rather simply cut and pasted the next line from the instructions : > > # wget http://www.digikam.org/drupal/system/files/libkexiv2cmake.diff_.txt > -O ../libkexiv2cmake.diff > > I then got as far as halfway through the digiKam build exercise. Seems like > I hit a brick wall because I was told "-- Configuring incomplete, errors > occurred!" > > It seems this is because apparently I don't have libkipi, libkexiv2 nor > libkdcraw installed. Huh?? I followed the instructions precisely up to this > point (a point for those who'd like to know exactly what I did, the > instructions via the above link will be a guidleine). Shouldn't these > libraries therefore be installed? Are the instructions lacking? > > Can somebody please pull me out of the quagmire? > > Here are the details... > > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ cmake > -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. > -- The C compiler identification is GNU > -- The CXX compiler identification is GNU > -- Check for working C compiler: /usr/bin/gcc > -- Check for working C compiler: /usr/bin/gcc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Looking for Q_WS_X11 > -- Looking for Q_WS_X11 - found > -- Looking for Q_WS_WIN > -- Looking for Q_WS_WIN - not found. > -- Looking for Q_WS_QWS > -- Looking for Q_WS_QWS - not found. > -- Looking for Q_WS_MAC > -- Looking for Q_WS_MAC - not found. > -- Found Qt-Version 4.7.0 (using /usr/bin/qmake) > -- Looking for XOpenDisplay in > /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so > -- Looking for XOpenDisplay in > /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so > - found > -- Looking for gethostbyname > -- Looking for gethostbyname - found > -- Looking for connect > -- Looking for connect - found > -- Looking for remove > -- Looking for remove - found > -- Looking for shmat > -- Looking for shmat - found > -- Looking for IceConnectionNumber in ICE > -- Looking for IceConnectionNumber in ICE - found > -- Found X11: /usr/lib/libX11.so > -- Looking for include files CMAKE_HAVE_PTHREAD_H > -- Looking for include files CMAKE_HAVE_PTHREAD_H - found > -- Looking for pthread_create in pthreads > -- Looking for pthread_create in pthreads - not found > -- Looking for pthread_create in pthread > -- Looking for pthread_create in pthread - found > -- Found Threads: TRUE > -- Looking for _POSIX_TIMERS > -- Looking for _POSIX_TIMERS - found > -- Found Automoc4: /usr/bin/automoc4 > -- Found Perl: /usr/bin/perl > -- Found Phonon: /usr/include (found version "4.4.2", required is "4.3.80") > -- Performing Test _OFFT_IS_64BIT > -- Performing Test _OFFT_IS_64BIT - Failed > -- Performing Test HAVE_FPIE_SUPPORT > -- Performing Test HAVE_FPIE_SUPPORT - Success > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success > -- Performing Test __KDE_HAVE_GCC_VISIBILITY > -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success > -- Found KDE 4.5 include dir: /usr/include > -- Found KDE 4.5 library dir: /usr/lib > -- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler > -- Found automoc4: /usr/bin/automoc4 > -- checking for module 'lcms' > -- found lcms, version 1.18 > -- Found lcms version 1.18, /usr/lib/liblcms.so > -- Found JPEG: /usr/lib/libjpeg.so > -- Found ZLIB: /usr/include > -- Found PNG: /usr/lib/libpng.so > -- Found TIFF: /usr/lib/libtiff.so > -- Found Jasper: /usr/lib/libjasper.so > -- Check Kdcraw library in local sub-folder... > -- Check Kdcraw library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- PKGCONFIG() indicates that libkdcraw is not installed (install the > package which contains libkdcraw.pc if you want to support this feature) > -- Check Kexiv2 library in local sub-folder... > -- Check Kexiv2 library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- PKGCONFIG() indicates that libkexiv2 is not installed (install the > package which contains libkexiv2.pc if you want to support this feature) > -- Check Kipi library in local sub-folder... > -- Check Kipi library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- PKGCONFIG() indicates that libkipi is not installed (install the package > which contains libkipi.pc if you want to support this feature) > -- checking for module 'libpgf' > -- package 'libpgf' not found > -- Could NOT find any working clapack installation > -- Identified libjpeg version: 62 > -- checking for module 'libkdcraw>=1.1.0' > -- package 'libkdcraw>=1.1.0' not found > -- checking for module 'libkexiv2>=1.1.0' > -- package 'libkexiv2>=1.1.0' not found > -- Found MySQL server executable at: /usr/sbin/mysqld > -- Found MySQL install_db executable at: /usr/bin/mysql_install_db > -- Found gphoto2: -L/usr/lib -lgphoto2_port;-L/usr/lib -lgphoto2 > -lgphoto2_port -lm > -- Found KdepimLibs: /usr/lib/cmake/KdepimLibs/KdepimLibsConfig.cmake > -- Found Marble: /usr/lib/libmarblewidget.so > -- Can build Marble plugin: yes > -- Found GLIB2: /usr/lib/libglib-2.0.so > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- Found LensFun: /usr/include > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- Performing Test HAVE_LQR_0_4 > -- Performing Test HAVE_LQR_0_4 - Success > -- Found Lqr-1: /usr/include/lqr-1 > -- Found Soprano: /usr/include > -- Found SharedDesktopOntologies: /usr/share/ontology > -- Found Nepomuk: /usr/lib/libnepomuk.so > -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) > -- > -- > ---------------------------------------------------------------------------------- > -- digiKam 1.8.0 dependencies results <http://www.digikam.org> > -- > -- Qt4 SQL module found..................... YES > -- MySQL Server found....................... YES > -- MySQL install_db tool found.............. YES > -- libtiff library found.................... YES > -- libpng library found..................... YES > -- libjasper library found.................. YES > -- liblcms library found.................... YES > -- libkipi library found.................... NO > -- > CMake Error at CMakeLists.txt:86 (MESSAGE): > digiKam needs libkipi. You need to install the libkipi (version >= 0.2.0) > library development package. > Call Stack (most recent call first): > CMakeLists.txt:285 (PRINT_LIBRARY_STATUS) > > > -- libkipi website is at http://www.digikam.org/sharedlibs > -- > -- libkexiv2 library found.................. NO > -- > CMake Error at CMakeLists.txt:86 (MESSAGE): > digiKam needs libkexiv2. You need to install the libkexiv2 (version >= > 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:286 (PRINT_LIBRARY_STATUS) > > > -- libkexiv2 website is at http://www.digikam.org/sharedlibs > -- > -- libkdcraw library found.................. NO > -- > CMake Error at CMakeLists.txt:86 (MESSAGE): > digiKam needs libkdcraw. You need to install the libkdcraw (version >= > 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:287 (PRINT_LIBRARY_STATUS) > > > -- libkdcraw website is at http://www.digikam.org/sharedlibs > -- > -- libpgf library found..................... NO (optional - internal > version used instead) > -- libclapack library found................. NO (optional - internal > version used instead) > -- libgphoto2 library found................. YES (optional) > -- libkdepimlibs library found.............. YES (optional) > -- libmarblewidget library found............ YES (optional) > -- Can build Marble plugin.................. YES (optional) > -- Nepomuk libraries found.................. YES (optional) > -- libglib2 library found................... YES (optional) > -- liblqr-1 library found................... YES (optional) > -- liblensfun library found................. YES (optional) > -- Doxygen found............................ NO (optional) > -- > -- You will not be able to to generate the API documentation. > -- This does not affect building digiKam in any way. > -- > CMake Error at CMakeLists.txt:399 (MESSAGE): > digiKam will be compiled................. NO (Look README file for more > details about dependencies) > > > -- Configuring incomplete, errors occurred! > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ ^C > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ > > > On Sun, 2010-12-19 at 22:21 -0600, Hevï Guy wrote: > > First problem encountered... > > Following the instructions given at > http://www.digikam.org/drupal/download/SvnAlongStable I've been able to get > as far as "Patch CMakeLists.txt to be able to build standalone. Download > appended patch and place it in your development folder." I found the > original CMakeLists.txt on my boat trunk/libkeeiv2/ and, I found the patch > via the link: > > Index: CMakeLists.txt > > =================================================================== > --- CMakeLists.txt (Revision 1117624) > +++ CMakeLists.txt (Arbeitskopie) > @@ -1,5 +1,20 @@ > PROJECT(libkexiv2) > > +FIND_PACKAGE(KDE4 REQUIRED) > +INCLUDE(KDE4Defaults) > +INCLUDE(MacroLibrary) > +INCLUDE(MacroOptionalAddSubdirectory) > +INCLUDE(FindPackageHandleStandardArgs) > + > +ADD_DEFINITIONS (${QT_DEFINITIONS} ${QT_QTDBUS_DEFINITIONS} > ${KDE4_DEFINITIONS}) > +INCLUDE_DIRECTORIES (${QDBUS_INCLUDE_DIRS} ${CMAKE_SOURCE_DIR} > ${CMAKE_BINARY_DIR} ${KDE4_INCLUDES}) > + > +# Preview acess was added in Exiv2 0.18 > +# IMPORTANT : Several fixes done in 0.19. Set as default version when KDE > 4.4 will be released > +set(EXIV2_MIN_VERSION "0.18") > +macro_optional_find_package(Exiv2) > +macro_log_feature(EXIV2_FOUND "Exiv2" "A library to access image metadata" > "http://www.exiv2.org" FALSE ${EXIV2_MIN_VERSION} "Required to build > libkexiv2 and gwenview.") > + > # ======================================================= > # Information to update before to release this library. > > I assume that I copy the above and paste it into CMakeLists.txt. Is this > correct? Where do I append it? At the beginning? At the end? > > > On Sun, 2010-12-19 at 19:58 +0100, Michael G. Hansen wrote: > > On 12/19/2010 07:50 PM, Hevï Guy wrote: >> Thank-you Michael. A few more Noob questions: >> >> If I am somehow successful in getting DigiKam running by following what >> seems to be a complete set of instructions in your link, how would I >> then delete the stable version? > > You would have to uninstall it using the package management tools of > your distribution - for ubuntu, 'sudo apt-get remove digikam'. However, > you should first remove it, otherwise your installation overwrites the > files which apt-get thinks are in the package, and then they may be > removed when you uninstall. > >> Will it be safe to delete the development folder and contents after a >> successful build (I assume that the build also makes all the appropriate >> directories and populates the files accordingly, right?). > > Once you ran 'make install', yes, you can remove the build folder. > > Michael > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by J Albrecht
On Monday 20 Dec 2010 12:46:54 Hevï Guy wrote:
> Well, I decided to blast through on my own. I didn't "patch" anything > but rather simply cut and pasted the next line from the instructions : > > # wget > http://www.digikam.org/drupal/system/files/libkexiv2cmake.diff_.txt > -O ../libkexiv2cmake.diff > > I then got as far as halfway through the digiKam build exercise. Seems > like I hit a brick wall because I was told "-- Configuring incomplete, > errors occurred!" > > It seems this is because apparently I don't have libkipi, libkexiv2 nor > libkdcraw installed. Huh?? I followed the instructions precisely up to > this point (a point for those who'd like to know exactly what I did, the > instructions via the above link will be a guidleine). Shouldn't these > libraries therefore be installed? Are the instructions lacking? > > Can somebody please pull me out of the quagmire? You need to install the appropriate -dev packages, that's what it's complaining about. eg sudo apt-get install libkipi-dev libkdcraw-dev The dev packages contain the files necessary for other builds to link against those libraries. And if you don't know what that means then you are meddling with forces that are beyond your control ;-) Mark > > Here are the details... > > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ cmake > -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. > -- The C compiler identification is GNU > -- The CXX compiler identification is GNU > -- Check for working C compiler: /usr/bin/gcc > -- Check for working C compiler: /usr/bin/gcc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Looking for Q_WS_X11 > -- Looking for Q_WS_X11 - found > -- Looking for Q_WS_WIN > -- Looking for Q_WS_WIN - not found. > -- Looking for Q_WS_QWS > -- Looking for Q_WS_QWS - not found. > -- Looking for Q_WS_MAC > -- Looking for Q_WS_MAC - not found. > -- Found Qt-Version 4.7.0 (using /usr/bin/qmake) > -- Looking for XOpenDisplay > in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so > -- Looking for XOpenDisplay > in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so - found > -- Looking for gethostbyname > -- Looking for gethostbyname - found > -- Looking for connect > -- Looking for connect - found > -- Looking for remove > -- Looking for remove - found > -- Looking for shmat > -- Looking for shmat - found > -- Looking for IceConnectionNumber in ICE > -- Looking for IceConnectionNumber in ICE - found > -- Found X11: /usr/lib/libX11.so > -- Looking for include files CMAKE_HAVE_PTHREAD_H > -- Looking for include files CMAKE_HAVE_PTHREAD_H - found > -- Looking for pthread_create in pthreads > -- Looking for pthread_create in pthreads - not found > -- Looking for pthread_create in pthread > -- Looking for pthread_create in pthread - found > -- Found Threads: TRUE > -- Looking for _POSIX_TIMERS > -- Looking for _POSIX_TIMERS - found > -- Found Automoc4: /usr/bin/automoc4 > -- Found Perl: /usr/bin/perl > -- Found Phonon: /usr/include (found version "4.4.2", required is > "4.3.80") > -- Performing Test _OFFT_IS_64BIT > -- Performing Test _OFFT_IS_64BIT - Failed > -- Performing Test HAVE_FPIE_SUPPORT > -- Performing Test HAVE_FPIE_SUPPORT - Success > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success > -- Performing Test __KDE_HAVE_GCC_VISIBILITY > -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success > -- Found KDE 4.5 include dir: /usr/include > -- Found KDE 4.5 library dir: /usr/lib > -- Found the KDE4 kconfig_compiler > preprocessor: /usr/bin/kconfig_compiler > -- Found automoc4: /usr/bin/automoc4 > -- checking for module 'lcms' > -- found lcms, version 1.18 > -- Found lcms version 1.18, /usr/lib/liblcms.so > -- Found JPEG: /usr/lib/libjpeg.so > -- Found ZLIB: /usr/include > -- Found PNG: /usr/lib/libpng.so > -- Found TIFF: /usr/lib/libtiff.so > -- Found Jasper: /usr/lib/libjasper.so > -- Check Kdcraw library in local sub-folder... > -- Check Kdcraw library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- PKGCONFIG() indicates that libkdcraw is not installed (install the > package which contains libkdcraw.pc if you want to support this feature) > -- Check Kexiv2 library in local sub-folder... > -- Check Kexiv2 library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- PKGCONFIG() indicates that libkexiv2 is not installed (install the > package which contains libkexiv2.pc if you want to support this feature) > -- Check Kipi library in local sub-folder... > -- Check Kipi library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- PKGCONFIG() indicates that libkipi is not installed (install the > package which contains libkipi.pc if you want to support this feature) > -- checking for module 'libpgf' > -- package 'libpgf' not found > -- Could NOT find any working clapack installation > -- Identified libjpeg version: 62 > -- checking for module 'libkdcraw>=1.1.0' > -- package 'libkdcraw>=1.1.0' not found > -- checking for module 'libkexiv2>=1.1.0' > -- package 'libkexiv2>=1.1.0' not found > -- Found MySQL server executable at: /usr/sbin/mysqld > -- Found MySQL install_db executable at: /usr/bin/mysql_install_db > -- Found gphoto2: -L/usr/lib -lgphoto2_port;-L/usr/lib -lgphoto2 > -lgphoto2_port -lm > -- Found KdepimLibs: /usr/lib/cmake/KdepimLibs/KdepimLibsConfig.cmake > -- Found Marble: /usr/lib/libmarblewidget.so > -- Can build Marble plugin: yes > -- Found GLIB2: /usr/lib/libglib-2.0.so > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- Found LensFun: /usr/include > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- Performing Test HAVE_LQR_0_4 > -- Performing Test HAVE_LQR_0_4 - Success > -- Found Lqr-1: /usr/include/lqr-1 > -- Found Soprano: /usr/include > -- Found SharedDesktopOntologies: /usr/share/ontology > -- Found Nepomuk: /usr/lib/libnepomuk.so > -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) > >= 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:286 (PRINT_LIBRARY_STATUS) > > > -- libkexiv2 website is at http://www.digikam.org/sharedlibs > >= 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:287 (PRINT_LIBRARY_STATUS) > > > -- libkdcraw website is at http://www.digikam.org/sharedlibs > > First problem encountered... > > > > Following the instructions given at > > http://www.digikam.org/drupal/download/SvnAlongStable I've been able > > to get as far as "Patch CMakeLists.txt to be able to build standalone. > > Download appended patch and place it in your development folder." I > > found the original CMakeLists.txt on my boat trunk/libkeeiv2/ and, I > > found the patch via the link: > > > > Index: CMakeLists.txt > > > > =================================================================== > > --- CMakeLists.txt (Revision 1117624) > > +++ CMakeLists.txt (Arbeitskopie) > > @@ -1,5 +1,20 @@ > > PROJECT(libkexiv2) > > > > +FIND_PACKAGE(KDE4 REQUIRED) > > +INCLUDE(KDE4Defaults) > > +INCLUDE(MacroLibrary) > > +INCLUDE(MacroOptionalAddSubdirectory) > > +INCLUDE(FindPackageHandleStandardArgs) > > + > > +ADD_DEFINITIONS (${QT_DEFINITIONS} ${QT_QTDBUS_DEFINITIONS} ${KDE4_DEFINITIONS}) > > +INCLUDE_DIRECTORIES (${QDBUS_INCLUDE_DIRS} ${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR} ${KDE4_INCLUDES}) > > + > > +# Preview acess was added in Exiv2 0.18 > > +# IMPORTANT : Several fixes done in 0.19. Set as default version when KDE 4.4 will be released > > +set(EXIV2_MIN_VERSION "0.18") > > +macro_optional_find_package(Exiv2) > > +macro_log_feature(EXIV2_FOUND "Exiv2" "A library to access image metadata" "http://www.exiv2.org" FALSE ${EXIV2_MIN_VERSION} "Required to build libkexiv2 and gwenview.") > > + > > # ======================================================= > > # Information to update before to release this library. > > > > > > I assume that I copy the above and paste it into CMakeLists.txt. Is > > this correct? Where do I append it? At the beginning? At the end? > > > > > > On Sun, 2010-12-19 at 19:58 +0100, Michael G. Hansen wrote: > > > > > On 12/19/2010 07:50 PM, Hevï Guy wrote: > > > > Thank-you Michael. A few more Noob questions: > > > > > > > > If I am somehow successful in getting DigiKam running by following what > > > > seems to be a complete set of instructions in your link, how would I > > > > then delete the stable version? > > > > > > You would have to uninstall it using the package management tools of > > > your distribution - for ubuntu, 'sudo apt-get remove digikam'. However, > > > you should first remove it, otherwise your installation overwrites the > > > files which apt-get thinks are in the package, and then they may be > > > removed when you uninstall. > > > > > > > Will it be safe to delete the development folder and contents after a > > > > successful build (I assume that the build also makes all the appropriate > > > > directories and populates the files accordingly, right?). > > > > > > Once you ran 'make install', yes, you can remove the build folder. > > > > > > Michael > > > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Bugzilla from gert.kello@gmail.com
Hallo Gert,
Thanks for your kind assistance. Yes, apparently something didn't get installed. However, if this is the case, then perhaps something is missing in the instructions since I had followed them explicitly. I **really* appreciate you taking the time to write a script :) It seems very straight-forward compared to what was on the digiKam page. However (again, please pardon the Newbieism) what do I do about everything that I had completed thus far? Is it safe to simply delete the entire trunk directory and start from Ground Zero with the script? On Mon, 2010-12-20 at 15:13 +0200, Gert Kello wrote: Hi. Seems like something did not got installed. I assume You did successfully compile and install exiv2? I mixed a script for You based on http://www.digikam.org/drupal/download/KDE4 I would say You could use -DCMAKE_INSTALL_PREFIX=/usr instead of -DCMAKE_INSTALL_PREFIX=/usr/local (the -DCMAKE_INSTALL_PREFIX=/usr would overwrite the "stable" version of digikam, so "not along stable") svn co -N svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegraphics cd kdegraphics svn up libs svn up cmake cd .. svn co -N svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics cd graphics svn up digikam svn up kipi-plugins svn up cmake cd ../kdegraphics mkdir build cd build cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. make sudo make install cd ../../graphics mkdir build cd build cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. make sudo make install On 20 December 2010 14:46, Hevï Guy <[hidden email]> wrote: > Well, I decided to blast through on my own. I didn't "patch" anything but > rather simply cut and pasted the next line from the instructions : > > # wget http://www.digikam.org/drupal/system/files/libkexiv2cmake.diff_.txt > -O ../libkexiv2cmake.diff > > I then got as far as halfway through the digiKam build exercise. Seems like > I hit a brick wall because I was told "-- Configuring incomplete, errors > occurred!" > > It seems this is because apparently I don't have libkipi, libkexiv2 nor > libkdcraw installed. Huh?? I followed the instructions precisely up to this > point (a point for those who'd like to know exactly what I did, the > instructions via the above link will be a guidleine). Shouldn't these > libraries therefore be installed? Are the instructions lacking? > > Can somebody please pull me out of the quagmire? > > Here are the details... > > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ cmake > -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. > -- The C compiler identification is GNU > -- The CXX compiler identification is GNU > -- Check for working C compiler: /usr/bin/gcc > -- Check for working C compiler: /usr/bin/gcc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Looking for Q_WS_X11 > -- Looking for Q_WS_X11 - found > -- Looking for Q_WS_WIN > -- Looking for Q_WS_WIN - not found. > -- Looking for Q_WS_QWS > -- Looking for Q_WS_QWS - not found. > -- Looking for Q_WS_MAC > -- Looking for Q_WS_MAC - not found. > -- Found Qt-Version 4.7.0 (using /usr/bin/qmake) > -- Looking for XOpenDisplay in > /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so > -- Looking for XOpenDisplay in > /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so > - found > -- Looking for gethostbyname > -- Looking for gethostbyname - found > -- Looking for connect > -- Looking for connect - found > -- Looking for remove > -- Looking for remove - found > -- Looking for shmat > -- Looking for shmat - found > -- Looking for IceConnectionNumber in ICE > -- Looking for IceConnectionNumber in ICE - found > -- Found X11: /usr/lib/libX11.so > -- Looking for include files CMAKE_HAVE_PTHREAD_H > -- Looking for include files CMAKE_HAVE_PTHREAD_H - found > -- Looking for pthread_create in pthreads > -- Looking for pthread_create in pthreads - not found > -- Looking for pthread_create in pthread > -- Looking for pthread_create in pthread - found > -- Found Threads: TRUE > -- Looking for _POSIX_TIMERS > -- Looking for _POSIX_TIMERS - found > -- Found Automoc4: /usr/bin/automoc4 > -- Found Perl: /usr/bin/perl > -- Found Phonon: /usr/include (found version "4.4.2", required is "4.3.80") > -- Performing Test _OFFT_IS_64BIT > -- Performing Test _OFFT_IS_64BIT - Failed > -- Performing Test HAVE_FPIE_SUPPORT > -- Performing Test HAVE_FPIE_SUPPORT - Success > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success > -- Performing Test __KDE_HAVE_GCC_VISIBILITY > -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success > -- Found KDE 4.5 include dir: /usr/include > -- Found KDE 4.5 library dir: /usr/lib > -- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler > -- Found automoc4: /usr/bin/automoc4 > -- checking for module 'lcms' > -- found lcms, version 1.18 > -- Found lcms version 1.18, /usr/lib/liblcms.so > -- Found JPEG: /usr/lib/libjpeg.so > -- Found ZLIB: /usr/include > -- Found PNG: /usr/lib/libpng.so > -- Found TIFF: /usr/lib/libtiff.so > -- Found Jasper: /usr/lib/libjasper.so > -- Check Kdcraw library in local sub-folder... > -- Check Kdcraw library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- PKGCONFIG() indicates that libkdcraw is not installed (install the > package which contains libkdcraw.pc if you want to support this feature) > -- Check Kexiv2 library in local sub-folder... > -- Check Kexiv2 library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- PKGCONFIG() indicates that libkexiv2 is not installed (install the > package which contains libkexiv2.pc if you want to support this feature) > -- Check Kipi library in local sub-folder... > -- Check Kipi library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- PKGCONFIG() indicates that libkipi is not installed (install the package > which contains libkipi.pc if you want to support this feature) > -- checking for module 'libpgf' > -- package 'libpgf' not found > -- Could NOT find any working clapack installation > -- Identified libjpeg version: 62 > -- checking for module 'libkdcraw>=1.1.0' > -- package 'libkdcraw>=1.1.0' not found > -- checking for module 'libkexiv2>=1.1.0' > -- package 'libkexiv2>=1.1.0' not found > -- Found MySQL server executable at: /usr/sbin/mysqld > -- Found MySQL install_db executable at: /usr/bin/mysql_install_db > -- Found gphoto2: -L/usr/lib -lgphoto2_port;-L/usr/lib -lgphoto2 > -lgphoto2_port -lm > -- Found KdepimLibs: /usr/lib/cmake/KdepimLibs/KdepimLibsConfig.cmake > -- Found Marble: /usr/lib/libmarblewidget.so > -- Can build Marble plugin: yes > -- Found GLIB2: /usr/lib/libglib-2.0.so > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- Found LensFun: /usr/include > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig > -- Performing Test HAVE_LQR_0_4 > -- Performing Test HAVE_LQR_0_4 - Success > -- Found Lqr-1: /usr/include/lqr-1 > -- Found Soprano: /usr/include > -- Found SharedDesktopOntologies: /usr/share/ontology > -- Found Nepomuk: /usr/lib/libnepomuk.so > -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) > -- > -- > ---------------------------------------------------------------------------------- > -- digiKam 1.8.0 dependencies results <http://www.digikam.org> > -- > -- Qt4 SQL module found..................... YES > -- MySQL Server found....................... YES > -- MySQL install_db tool found.............. YES > -- libtiff library found.................... YES > -- libpng library found..................... YES > -- libjasper library found.................. YES > -- liblcms library found.................... YES > -- libkipi library found.................... NO > -- > CMake Error at CMakeLists.txt:86 (MESSAGE): > digiKam needs libkipi. You need to install the libkipi (version >= 0.2.0) > library development package. > Call Stack (most recent call first): > CMakeLists.txt:285 (PRINT_LIBRARY_STATUS) > > > -- libkipi website is at http://www.digikam.org/sharedlibs > -- > -- libkexiv2 library found.................. NO > -- > CMake Error at CMakeLists.txt:86 (MESSAGE): > digiKam needs libkexiv2. You need to install the libkexiv2 (version >= > 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:286 (PRINT_LIBRARY_STATUS) > > > -- libkexiv2 website is at http://www.digikam.org/sharedlibs > -- > -- libkdcraw library found.................. NO > -- > CMake Error at CMakeLists.txt:86 (MESSAGE): > digiKam needs libkdcraw. You need to install the libkdcraw (version >= > 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:287 (PRINT_LIBRARY_STATUS) > > > -- libkdcraw website is at http://www.digikam.org/sharedlibs > -- > -- libpgf library found..................... NO (optional - internal > version used instead) > -- libclapack library found................. NO (optional - internal > version used instead) > -- libgphoto2 library found................. YES (optional) > -- libkdepimlibs library found.............. YES (optional) > -- libmarblewidget library found............ YES (optional) > -- Can build Marble plugin.................. YES (optional) > -- Nepomuk libraries found.................. YES (optional) > -- libglib2 library found................... YES (optional) > -- liblqr-1 library found................... YES (optional) > -- liblensfun library found................. YES (optional) > -- Doxygen found............................ NO (optional) > -- > -- You will not be able to to generate the API documentation. > -- This does not affect building digiKam in any way. > -- > CMake Error at CMakeLists.txt:399 (MESSAGE): > digiKam will be compiled................. NO (Look README file for more > details about dependencies) > > > -- Configuring incomplete, errors occurred! > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ ^C > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ > > > On Sun, 2010-12-19 at 22:21 -0600, Hevï Guy wrote: > > First problem encountered... > > Following the instructions given at > http://www.digikam.org/drupal/download/SvnAlongStable I've been able to get > as far as "Patch CMakeLists.txt to be able to build standalone. Download > appended patch and place it in your development folder." I found the > original CMakeLists.txt on my boat trunk/libkeeiv2/ and, I found the patch > via the link: > > Index: CMakeLists.txt > > =================================================================== > --- CMakeLists.txt (Revision 1117624) > +++ CMakeLists.txt (Arbeitskopie) > @@ -1,5 +1,20 @@ > PROJECT(libkexiv2) > > +FIND_PACKAGE(KDE4 REQUIRED) > +INCLUDE(KDE4Defaults) > +INCLUDE(MacroLibrary) > +INCLUDE(MacroOptionalAddSubdirectory) > +INCLUDE(FindPackageHandleStandardArgs) > + > +ADD_DEFINITIONS (${QT_DEFINITIONS} ${QT_QTDBUS_DEFINITIONS} > ${KDE4_DEFINITIONS}) > +INCLUDE_DIRECTORIES (${QDBUS_INCLUDE_DIRS} ${CMAKE_SOURCE_DIR} > ${CMAKE_BINARY_DIR} ${KDE4_INCLUDES}) > + > +# Preview acess was added in Exiv2 0.18 > +# IMPORTANT : Several fixes done in 0.19. Set as default version when KDE > 4.4 will be released > +set(EXIV2_MIN_VERSION "0.18") > +macro_optional_find_package(Exiv2) > +macro_log_feature(EXIV2_FOUND "Exiv2" "A library to access image metadata" > "http://www.exiv2.org" FALSE ${EXIV2_MIN_VERSION} "Required to build > libkexiv2 and gwenview.") > + > # ======================================================= > # Information to update before to release this library. > > I assume that I copy the above and paste it into CMakeLists.txt. Is this > correct? Where do I append it? At the beginning? At the end? > > > On Sun, 2010-12-19 at 19:58 +0100, Michael G. Hansen wrote: > > On 12/19/2010 07:50 PM, Hevï Guy wrote: >> Thank-you Michael. A few more Noob questions: >> >> If I am somehow successful in getting DigiKam running by following what >> seems to be a complete set of instructions in your link, how would I >> then delete the stable version? > > You would have to uninstall it using the package management tools of > your distribution - for ubuntu, 'sudo apt-get remove digikam'. However, > you should first remove it, otherwise your installation overwrites the > files which apt-get thinks are in the package, and then they may be > removed when you uninstall. > >> Will it be safe to delete the development folder and contents after a >> successful build (I assume that the build also makes all the appropriate >> directories and populates the files accordingly, right?). > > Once you ran 'make install', yes, you can remove the build folder. > > Michael > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Mark Greenwood
On Mon, 2010-12-20 at 13:14 +0000, Mark Greenwood wrote: You need to install the appropriate -dev packages, that's what it's complaining about. eg sudo apt-get install libkipi-dev libkdcraw-dev I was relying on the script at the digiKam site to have made me do this as I followed the lines, step-by-step. Seems that some critical lines were missing. Indeed, I know what that means. And yes, I am most definitely meddling with forces that are well beyond my control. Alas, I have no choice if I want to get this program behaving properly :( Thus, I plod onwards through a dangerous minefield!The dev packages contain the files necessary for other builds to link against those libraries. And if you don't know what that means then you are meddling with forces that are beyond your control ;-) Mark > > Here are the details... > > heviiguy@hevii-NtBk-2:~/trunk/digikam/build$ cmake > -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=/usr/local .. > -- The C compiler identification is GNU > -- The CXX compiler identification is GNU > -- Check for working C compiler: /usr/bin/gcc > -- Check for working C compiler: /usr/bin/gcc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Looking for Q_WS_X11 > -- Looking for Q_WS_X11 - found > -- Looking for Q_WS_WIN > -- Looking for Q_WS_WIN - not found. > -- Looking for Q_WS_QWS > -- Looking for Q_WS_QWS - not found. > -- Looking for Q_WS_MAC > -- Looking for Q_WS_MAC - not found. > -- Found Qt-Version 4.7.0 (using /usr/bin/qmake) > -- Looking for XOpenDisplay > in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so > -- Looking for XOpenDisplay > in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so - found > -- Looking for gethostbyname > -- Looking for gethostbyname - found > -- Looking for connect > -- Looking for connect - found > -- Looking for remove > -- Looking for remove - found > -- Looking for shmat > -- Looking for shmat - found > -- Looking for IceConnectionNumber in ICE > -- Looking for IceConnectionNumber in ICE - found > -- Found X11: /usr/lib/libX11.so > -- Looking for include files CMAKE_HAVE_PTHREAD_H > -- Looking for include files CMAKE_HAVE_PTHREAD_H - found > -- Looking for pthread_create in pthreads > -- Looking for pthread_create in pthreads - not found > -- Looking for pthread_create in pthread > -- Looking for pthread_create in pthread - found > -- Found Threads: TRUE > -- Looking for _POSIX_TIMERS > -- Looking for _POSIX_TIMERS - found > -- Found Automoc4: /usr/bin/automoc4 > -- Found Perl: /usr/bin/perl > -- Found Phonon: /usr/include (found version "4.4.2", required is > "4.3.80") > -- Performing Test _OFFT_IS_64BIT > -- Performing Test _OFFT_IS_64BIT - Failed > -- Performing Test HAVE_FPIE_SUPPORT > -- Performing Test HAVE_FPIE_SUPPORT - Success > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL > -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success > -- Performing Test __KDE_HAVE_GCC_VISIBILITY > -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success > -- Found KDE 4.5 include dir: /usr/include > -- Found KDE 4.5 library dir: /usr/lib > -- Found the KDE4 kconfig_compiler > preprocessor: /usr/bin/kconfig_compiler > -- Found automoc4: /usr/bin/automoc4 > -- checking for module 'lcms' > -- found lcms, version 1.18 > -- Found lcms version 1.18, /usr/lib/liblcms.so > -- Found JPEG: /usr/lib/libjpeg.so > -- Found ZLIB: /usr/include > -- Found PNG: /usr/lib/libpng.so > -- Found TIFF: /usr/lib/libtiff.so > -- Found Jasper: /usr/lib/libjasper.so > -- Check Kdcraw library in local sub-folder... > -- Check Kdcraw library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- PKGCONFIG() indicates that libkdcraw is not installed (install the > package which contains libkdcraw.pc if you want to support this feature) > -- Check Kexiv2 library in local sub-folder... > -- Check Kexiv2 library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- PKGCONFIG() indicates that libkexiv2 is not installed (install the > package which contains libkexiv2.pc if you want to support this feature) > -- Check Kipi library in local sub-folder... > -- Check Kipi library using pkg-config... > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- PKGCONFIG() indicates that libkipi is not installed (install the > package which contains libkipi.pc if you want to support this feature) > -- checking for module 'libpgf' > -- package 'libpgf' not found > -- Could NOT find any working clapack installation > -- Identified libjpeg version: 62 > -- checking for module 'libkdcraw>=1.1.0' > -- package 'libkdcraw>=1.1.0' not found > -- checking for module 'libkexiv2>=1.1.0' > -- package 'libkexiv2>=1.1.0' not found > -- Found MySQL server executable at: /usr/sbin/mysqld > -- Found MySQL install_db executable at: /usr/bin/mysql_install_db > -- Found gphoto2: -L/usr/lib -lgphoto2_port;-L/usr/lib -lgphoto2 > -lgphoto2_port -lm > -- Found KdepimLibs: /usr/lib/cmake/KdepimLibs/KdepimLibsConfig.cmake > -- Found Marble: /usr/lib/libmarblewidget.so > -- Can build Marble plugin: yes > -- Found GLIB2: /usr/lib/libglib-2.0.so > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- Found LensFun: /usr/include > -- WARNING: you are using the obsolete 'PKGCONFIG' macro use > FindPkgConfig > -- Performing Test HAVE_LQR_0_4 > -- Performing Test HAVE_LQR_0_4 - Success > -- Found Lqr-1: /usr/include/lqr-1 > -- Found Soprano: /usr/include > -- Found SharedDesktopOntologies: /usr/share/ontology > -- Found Nepomuk: /usr/lib/libnepomuk.so > -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) > >= 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:286 (PRINT_LIBRARY_STATUS) > > > -- libkexiv2 website is at http://www.digikam.org/sharedlibs > >= 1.1.0) library development package. > Call Stack (most recent call first): > CMakeLists.txt:287 (PRINT_LIBRARY_STATUS) > > > -- libkdcraw website is at http://www.digikam.org/sharedlibs > > First problem encountered... > > > > Following the instructions given at > > http://www.digikam.org/drupal/download/SvnAlongStable I've been able > > to get as far as "Patch CMakeLists.txt to be able to build standalone. > > Download appended patch and place it in your development folder." I > > found the original CMakeLists.txt on my boat trunk/libkeeiv2/ and, I > > found the patch via the link: > > > > Index: CMakeLists.txt > > > > =================================================================== > > --- CMakeLists.txt (Revision 1117624) > > +++ CMakeLists.txt (Arbeitskopie) > > @@ -1,5 +1,20 @@ > > PROJECT(libkexiv2) > > > > +FIND_PACKAGE(KDE4 REQUIRED) > > +INCLUDE(KDE4Defaults) > > +INCLUDE(MacroLibrary) > > +INCLUDE(MacroOptionalAddSubdirectory) > > +INCLUDE(FindPackageHandleStandardArgs) > > + > > +ADD_DEFINITIONS (${QT_DEFINITIONS} ${QT_QTDBUS_DEFINITIONS} ${KDE4_DEFINITIONS}) > > +INCLUDE_DIRECTORIES (${QDBUS_INCLUDE_DIRS} ${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR} ${KDE4_INCLUDES}) > > + > > +# Preview acess was added in Exiv2 0.18 > > +# IMPORTANT : Several fixes done in 0.19. Set as default version when KDE 4.4 will be released > > +set(EXIV2_MIN_VERSION "0.18") > > +macro_optional_find_package(Exiv2) > > +macro_log_feature(EXIV2_FOUND "Exiv2" "A library to access image metadata" "http://www.exiv2.org" FALSE ${EXIV2_MIN_VERSION} "Required to build libkexiv2 and gwenview.") > > + > > # ======================================================= > > # Information to update before to release this library. > > > > > > I assume that I copy the above and paste it into CMakeLists.txt. Is > > this correct? Where do I append it? At the beginning? At the end? > > > > > > On Sun, 2010-12-19 at 19:58 +0100, Michael G. Hansen wrote: > > > > > On 12/19/2010 07:50 PM, Hevï Guy wrote: > > > > Thank-you Michael. A few more Noob questions: > > > > > > > > If I am somehow successful in getting DigiKam running by following what > > > > seems to be a complete set of instructions in your link, how would I > > > > then delete the stable version? > > > > > > You would have to uninstall it using the package management tools of > > > your distribution - for ubuntu, 'sudo apt-get remove digikam'. However, > > > you should first remove it, otherwise your installation overwrites the > > > files which apt-get thinks are in the package, and then they may be > > > removed when you uninstall. > > > > > > > Will it be safe to delete the development folder and contents after a > > > > successful build (I assume that the build also makes all the appropriate > > > > directories and populates the files accordingly, right?). > > > > > > Once you ran 'make install', yes, you can remove the build folder. > > > > > > Michael > > > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by J Albrecht
I "think" that I'm picking up bits 'n' pieces of knowledge here and slowly expanding my knowledge. With this in mind, it seems that the script so kindly provided by Gert doesn't address the reason why I find myself in this very unfamiliar territory: The necessary exiv2 update. Or, does it?
If it doesn't, please have mercy on me. Perhaps someone can let me know exactly what else (and "where" in relation to the existing script) I need to enter into Terminal. I'm concerned that if I use the script I'm going to find myself back where I was when I first arrived here: A buggy digiKam program that won't play nicely with my Nikon D90. Many thanks for your continuing assistance and understanding! On Mon, 2010-12-20 at 08:13 -0600, Hevï Guy wrote: Hallo Gert, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |