Hello :-)
So, finally I tried to install the svn version, but with not much success :-( It seemed to go forward quite fine, but at the end it didn't work. I redirected all messages to a file, and as far as I can see, there are (at least) two messages that I don't understand: first was: configure: WARNING: libMagick is required for the jpeglossess plugin. and then: You're missing libMagick. The jpeglossless plugin will not be compiled. but libMagick is installed on my system and "locate libMagick" gives: /usr/lib/libMagick++.so.6 /usr/lib/libMagick++.so.6.2.3 /usr/lib/libMagick.so.6 /usr/lib/libMagick.so.6.2.3 ??? Then the messages end with: -- digiKam configure results ------------------- -- sqlite3 found.................. YES -- gphoto2 found.................. YES -- libkipi found.................. YES -- libtiff found.................. YES -- libpng found................... YES -- lcms found..................... YES -- Exiv2 library found............ NO digiKam needs Exiv2 library. You need to install Exiv2 first Exiv2 website is at http://www.exiv2.org ------------------------------------------------ -- digiKamImagePlugins configure results -------- -- digiKam found.................. YES ------------------------------------------------- I've installed exiv2 to /opt/digikam_exiv2 - but for sure did something wrong. I guess, I must somehow tell in the "compile_it"-script where exiv2 and libMagick are, but I have no idea, how to do that. Can you help me a step forward? and: I guess I have to recompile, do I have to do "make uninstall" and/or "make distclean" first, something else? I know, people that are so absolutely unaware shouldn't try to install svn-versions, but I'm so very curious..., so any help would be highly appreciated. regards Daniel --------------- here's some more information about what I did: - made a new user "test" on my system - logged in as "test" - downloaded and untared exiv2-0.9.1, then in that directory as "test": ./configure --prefix=/opt/digikam_exiv2 make su -l root (and cd to the said dirctory) make install - then (again as "test", in the same directory) run the script "compile_it" (from Markus Spring's mail to this list of April 6, without changes): source compile_it If you want to see the output of "compile_it" (197 KB) I'll tar it and send it as attachement. -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com special interest site: http://www.bauer-nudes.com _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Daniel Bauer wrote:
> and then: > You're missing libMagick. The jpeglossless plugin will not be compiled. > > but libMagick is installed on my system and "locate libMagick" gives: > /usr/lib/libMagick++.so.6 > /usr/lib/libMagick++.so.6.2.3 > /usr/lib/libMagick.so.6 > /usr/lib/libMagick.so.6.2.3 Debian/deb or RedHat/RPM package based system? (Or Gentoo etc?) Either way, those are the runtime libraries, not the -dev(el) packages required for compiling. > I've installed exiv2 to /opt/digikam_exiv2 - but for sure did something wrong. > I guess, I must somehow tell in the "compile_it"-script where exiv2 and > libMagick are, but I have no idea, how to do that. if [ $1 -eq 2 ]; then echo Get, compile and install digikam svn co -N svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics cd graphics svn up digikam svn up digikamimageplugins make -f Makefile.cvs LDFLAGS=-L/opt/exiv2/lib CXXFLAGS=-I/opt/exiv2/include ./configure --enable-debug=full make sudo make install fi Change the LDFLAGS and CXXFLAGS to match your installation paths for Exiv2. Be sure to use the SVN version of Exiv2 too :) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
Le Lundi 15 Mai 2006 07:16 PM, Daniel Bauer a écrit :
> Hello :-) > > So, finally I tried to install the svn version, but with not much success > :-( It seemed to go forward quite fine, but at the end it didn't work. I > redirected all messages to a file, and as far as I can see, there are (at > least) two messages that I don't understand: > first was: > > configure: WARNING: > libMagick is required for the jpeglossess plugin. > > and then: > You're missing libMagick. The jpeglossless plugin will not be compiled. > > but libMagick is installed on my system and "locate libMagick" gives: > /usr/lib/libMagick++.so.6 > /usr/lib/libMagick++.so.6.2.3 > /usr/lib/libMagick.so.6 > /usr/lib/libMagick.so.6.2.3 Arf. This is a strange behaviuors with suse... In all case, no need to recompile kipi-plugins and libkipi to test digikam from svn. You can use the libkipi developement package to recompile digikam. That all. > > ??? > > Then the messages end with: > -- digiKam configure results ------------------- > -- sqlite3 found.................. YES > -- gphoto2 found.................. YES > -- libkipi found.................. YES > -- libtiff found.................. YES > -- libpng found................... YES > -- lcms found..................... YES > -- Exiv2 library found............ NO > > digiKam needs Exiv2 library. You need to install Exiv2 first > Exiv2 website is at http://www.exiv2.org > ------------------------------------------------ > > -- digiKamImagePlugins configure results -------- > -- digiKam found.................. YES > ------------------------------------------------- > > I've installed exiv2 to /opt/digikam_exiv2 - but for sure did something > wrong. I guess, I must somehow tell in the "compile_it"-script where exiv2 > and libMagick are, but I have no idea, how to do that. > I suspect that /opt is the wrong way to install Exiv2. Here in Mandriva Exiv2 is installed to /usr using --prefix=/usr option. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Duncan Hill-5
Le Lundi 15 Mai 2006 07:53 PM, Duncan Hill a écrit :
> Daniel Bauer wrote: > > and then: > > You're missing libMagick. The jpeglossless plugin will not be compiled. > > > > but libMagick is installed on my system and "locate libMagick" gives: > > /usr/lib/libMagick++.so.6 > > /usr/lib/libMagick++.so.6.2.3 > > /usr/lib/libMagick.so.6 > > /usr/lib/libMagick.so.6.2.3 > > Debian/deb or RedHat/RPM package based system? (Or Gentoo etc?) > > Either way, those are the runtime libraries, not the -dev(el) packages > required for compiling. > > > I've installed exiv2 to /opt/digikam_exiv2 - but for sure did something > > wrong. I guess, I must somehow tell in the "compile_it"-script where > > exiv2 and libMagick are, but I have no idea, how to do that. > > if [ $1 -eq 2 ]; then > echo Get, compile and install digikam > svn co -N svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics > cd graphics > svn up digikam > svn up digikamimageplugins > make -f Makefile.cvs > LDFLAGS=-L/opt/exiv2/lib CXXFLAGS=-I/opt/exiv2/include ./configure > --enable-debug=full > make > sudo make install > fi > > Change the LDFLAGS and CXXFLAGS to match your installation paths for > Exiv2. Be sure to use the SVN version of Exiv2 too :) > Yes, Daniel. Exiv2 from svn is very improved against 0.9.1. There is a TIFF/EP parser (DNG, CR2, NEF, PAF, etc... files format), and a new minolta makernote parser (from me (:=)))... In digikam from svn there is a MRW parser witch will be moved into Exiv2 later. Gilles > _______________________________________________ > 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 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Caulier Gilles wrote: > Yes, Daniel. Exiv2 from svn is very improved against 0.9.1. There is a TIFF/EP > parser (DNG, CR2, NEF, PAF, etc... files format), and a new minolta makernote > parser (from me (:=)))... In digikam from svn there is a MRW parser witch > will be moved into Exiv2 later. I succeeded in compiling exiv2 and digikam both from svn By default, exiv2 installs itself under /usr/local, and this library path is searched when configuring and compiling digikam. For exiv2: mkdir exiv2_svn cd exiv2_svn/ svn checkout svn://dev.robotbattle.com/exiv2/trunk . make config ./configure make make install (I prefer to use checkinstall instead of make install, this program creates uninstallable packages, in my case for debian) The compilation of digikam (from svn) as well as ufraw 0.8.1 went flawless then. Regards - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEaNXvxxUzQSse11ARApEkAJ0R0AxacFS4MLyFi4zIxk82J5xB4gCfd1as 4uNYRsjuocytes+SW1V7tG4= =JW5u -----END PGP SIGNATURE----- _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Gilles Caulier-2
Am Montag, 15. Mai 2006 20:19 schrieb Caulier Gilles: > Arf. This is a strange behaviuors with suse... I LOVE Suse, hehe However, it's the only Linux I know :-) > > I suspect that /opt is the wrong way to install Exiv2. Here in Mandriva > Exiv2 is installed to /usr using --prefix=/usr option. > I have now installed exiv2 svn "as is" (no --prefix), and with the commands Duncan Hill gave me, it works. I only had a short view: it looks very good, and it also looks like a lot of work behind it of you and the developers team! I'll take my time to have a closer look soon and give feedback as soon as possible, although probably only next week, because I have to do a lot of new photos... new "food" for digiKam then :-) regards Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com special interest site: http://www.bauer-nudes.com _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Duncan Hill-5
Am Montag, 15. Mai 2006 19:53 schrieb Duncan Hill:
Thanks Duncan for your hints! I have the svn version now installed and running. > > but libMagick is installed on my system and "locate libMagick" gives: > > /usr/lib/libMagick++.so.6 > > /usr/lib/libMagick++.so.6.2.3 > > /usr/lib/libMagick.so.6 > > /usr/lib/libMagick.so.6.2.3 > > Debian/deb or RedHat/RPM package based system? (Or Gentoo etc?) Suse 10.0, KDE 3.5.1 > > Either way, those are the runtime libraries, not the -dev(el) packages > required for compiling. Yes, I really should have noticed this myself, zzz. > > > I've installed exiv2 to /opt/digikam_exiv2 - but for sure did something > > wrong. I guess, I must somehow tell in the "compile_it"-script where > > exiv2 and libMagick are, but I have no idea, how to do that. > > if [ $1 -eq 2 ]; then > echo Get, compile and install digikam > svn co -N svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics > cd graphics > svn up digikam > svn up digikamimageplugins > make -f Makefile.cvs > LDFLAGS=-L/opt/exiv2/lib CXXFLAGS=-I/opt/exiv2/include ./configure > --enable-debug=full > make > sudo make install > fi > > Change the LDFLAGS and CXXFLAGS to match your installation paths for > Exiv2. Be sure to use the SVN version of Exiv2 too :) > 0.8.1, but I could re-install it, and now have 0.8.1 normally installed and 0.9 svn in another directory. b.t.w. I don't know what the "if" above means. I first copied it to a file, made it a script/executable, but bash said, it doesn't know what $1 is... so i just copied every line by line (execpt if and fi) to the console and it worked. thanks again for your help and good night :-) Daniel ers -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com special interest site: http://www.bauer-nudes.com _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
Le Lundi 15 Mai 2006 10:28 PM, Daniel Bauer a écrit :
> Am Montag, 15. Mai 2006 20:19 schrieb Caulier Gilles: > > Arf. This is a strange behaviuors with suse... > > I LOVE Suse, hehe > However, it's the only Linux I know :-) > > > I suspect that /opt is the wrong way to install Exiv2. Here in Mandriva > > Exiv2 is installed to /usr using --prefix=/usr option. > > I have now installed exiv2 svn "as is" (no --prefix), and with the commands > Duncan Hill gave me, it works. > > I only had a short view: it looks very good, and it also looks like a lot > of work behind it of you and the developers team! I'll take my time to have > a closer look soon and give feedback as soon as possible, although probably > only next week, because I have to do a lot of new photos... new "food" for > digiKam then :-) > thanks Daniel ! Unforget to update source from svn reguliary. We working all day into digiKam. Also, take a look into NEWS and TODO files from svn. You can found list a new features, bugfix, and the jobs still to do. I think there is no major bugs in current implementation. I'm using 0.9.0-svn all day to develop and the code is now under polishing and finalization to publish the first 0.9.0 beta1 in some week (i hope) Take a care to make a new user and create a test database to prevent problems. Do not use it in production yet... Gilles > regards > > Daniel _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Am Montag, 15. Mai 2006 22:48 schrieb Caulier Gilles:
> thanks Daniel ! > > Unforget to update source from svn reguliary. We working all day into > digiKam. thanks for pointing this out. Sorry for another newbie-question then: On your website I read: "To Update the SVN copy later simply give this command from the directory above the digikam folder : # svn up digkam" on my PC the source-code (graphics and libs directory) are in /eigene/rpms-progs/digikam_svn, the install in /opt/digikam-svn is "the directory above the digikam folder" on my PC now /eigene/rpms-progs/ or /opt/ ??? and: after "svn up digkam", do I have to do # make -f Makefile.cvs # ./configure (+my prefix) # make # make install every time? Or is it already done with "svn up digkam"? > > Also, take a look into NEWS and TODO files from svn. You can found list a > new features, bugfix, and the jobs still to do. I will. > > I think there is no major bugs in current implementation. I'm using > 0.9.0-svn all day to develop and the code is now under polishing and > finalization to publish the first 0.9.0 beta1 in some week (i hope) > > Take a care to make a new user and create a test database to prevent > problems. I did so. > > Do not use it in production yet... > > Gilles > regards Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com special interest site: http://www.bauer-nudes.com _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tuesday 16 May 2006 10:04 am, Daniel Bauer wrote:
> Am Montag, 15. Mai 2006 22:48 schrieb Caulier Gilles: > > thanks Daniel ! > > > > Unforget to update source from svn reguliary. We working all day into > > digiKam. > > thanks for pointing this out. Sorry for another newbie-question then: > > On your website I read: > "To Update the SVN copy later simply give this command from the directory > above the digikam folder : > # svn up digkam" > > on my PC the source-code (graphics and libs directory) are > in /eigene/rpms-progs/digikam_svn, the install in /opt/digikam-svn > > is "the directory above the digikam folder" on my PC now > /eigene/rpms-progs/ or > /opt/ > ??? svn is a source code repository. You need to checkout the code where is your local copy : /eigene/rpms-progs/digikam_svn > > and: after "svn up digkam", do I have to do > > # make -f Makefile.cvs > # ./configure (+my prefix) > # make > # make install > > every time? > Or is it already done with "svn up digkam"? When you make a fresh checkout, you need to recompile and install digikam and DigikamImagePlugins. Normally, you jest nedd to do : # make # make install But sometimes, when some new implementation file have been added to svn, you need to rebuild all from scratch, like this : # make distclean # make -f Makefile.cvs # ./configure (+my prefix) # make # make install Using this way can take a while, but like this you prevent all binary uncompatibilty with all previous compilation. This is require because digikam isn't yet frozen about features (not yet beta1), but in a near future, the implementation will be stabilized (:=))) // ------------------------------------------------ Have you take a look about new Black & white converter. This tool have been the subject of long dicussions with you in the past about possible optimizations... Do you remember ? Like i'm a big fan of B&W pictures (I have learn photography with Ilford HP5+ analog film and my Dynax 700si camera), i would like to have a plain feedback from a pro-photographer (:=))) A nice day Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Am Dienstag, 16. Mai 2006 10:17 schrieb Gilles Caulier:
> > On your website I read: > > "To Update the SVN copy later simply give this command from the directory > > above the digikam folder : > > # svn up digkam" > > > > on my PC the source-code (graphics and libs directory) are > > in /eigene/rpms-progs/digikam_svn, the install in /opt/digikam-svn > > > > is "the directory above the digikam folder" on my PC now > > /eigene/rpms-progs/ or > > /opt/ > > ??? > > svn is a source code repository. You need to checkout the code where is > your local copy : /eigene/rpms-progs/digikam_svn > When you make a fresh checkout, you need to recompile and install digikam > and DigikamImagePlugins. Normally, you jest nedd to do : > > # make > # make install > > But sometimes, when some new implementation file have been added to svn, > you need to rebuild all from scratch, like this : > > # make distclean > # make -f Makefile.cvs > # ./configure (+my prefix) > # make > # make install > > > // ------------------------------------------------ > > Have you take a look about new Black & white converter. This tool have been > the subject of long dicussions with you in the past about possible > optimizations... Do you remember ? Yes I remember, of course :-) I'll take my time to have a deeper look at it this week-end. > > Like i'm a big fan of B&W pictures (I have learn photography with Ilford > HP5+ analog film and my Dynax 700si camera), i would like to have a plain > feedback from a pro-photographer (:=))) > > A nice day > > Gilles 2U2 Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com special interest site: http://www.bauer-nudes.com _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tuesday 16 May 2006 11:49 am, Daniel Bauer wrote:
> Am Dienstag, 16. Mai 2006 10:17 schrieb Gilles Caulier: > > > On your website I read: > > > "To Update the SVN copy later simply give this command from the > > > directory above the digikam folder : > > > # svn up digkam" > > > > > > on my PC the source-code (graphics and libs directory) are > > > in /eigene/rpms-progs/digikam_svn, the install in /opt/digikam-svn > > > > > > is "the directory above the digikam folder" on my PC now > > > /eigene/rpms-progs/ or > > > /opt/ > > > ??? > > > > svn is a source code repository. You need to checkout the code where is > > your local copy : /eigene/rpms-progs/digikam_svn > > When you make a fresh checkout, you need to recompile and install digikam > > and DigikamImagePlugins. Normally, you jest nedd to do : > > > > # make > > # make install > > > > But sometimes, when some new implementation file have been added to svn, > > you need to rebuild all from scratch, like this : > > > > # make distclean > > # make -f Makefile.cvs > > # ./configure (+my prefix) > > # make > > # make install > > Thanks for the details. IMPORTANT : the digiKam handbook is under construction by Gerhard Kulzer. It's a long task to do. Not all is complete. If you want some help about an option, for example to set properlly the ICC settings management or the RAW file decoding settings, i recommend you to read the contextual help for each option available using SHIFT+F1. Just click on widget from gui where you want more informations, like this for example : http://digikam3rdparty.free.fr/Screenshots/contextualhelp.png Note : this is me on the motorbike (:=))) Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
On Tuesday 16 May 2006 10:04, Daniel Bauer wrote:
> Am Montag, 15. Mai 2006 22:48 schrieb Caulier Gilles: > > thanks Daniel ! > > > > Unforget to update source from svn reguliary. We working all day into > > digiKam. > > thanks for pointing this out. Sorry for another newbie-question then: > > On your website I read: > "To Update the SVN copy later simply give this command from the directory > above the digikam folder : > # svn up digkam" > > on my PC the source-code (graphics and libs directory) are > in /eigene/rpms-progs/digikam_svn, the install in /opt/digikam-svn > > is "the directory above the digikam folder" on my PC now > /eigene/rpms-progs/ or > /opt/ > ??? > > and: after "svn up digkam", do I have to do > > # make -f Makefile.cvs > # ./configure (+my prefix) > # make > # make install > > every time? > Or is it already done with "svn up digkam"? No 'svn up' is just updating/downloading the sources. Makefile.cvs and configure you only have to do when a Makefile.am was in the updated files. Gerhard _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tuesday 16 May 2006 12:24 pm, Gerhard Kulzer wrote:
> On Tuesday 16 May 2006 10:04, Daniel Bauer wrote: > > Am Montag, 15. Mai 2006 22:48 schrieb Caulier Gilles: > > > thanks Daniel ! > > > > > > Unforget to update source from svn reguliary. We working all day into > > > digiKam. > > > > thanks for pointing this out. Sorry for another newbie-question then: > > > > On your website I read: > > "To Update the SVN copy later simply give this command from the directory > > above the digikam folder : > > # svn up digkam" > > > > on my PC the source-code (graphics and libs directory) are > > in /eigene/rpms-progs/digikam_svn, the install in /opt/digikam-svn > > > > is "the directory above the digikam folder" on my PC now > > /eigene/rpms-progs/ or > > /opt/ > > ??? > > > > and: after "svn up digkam", do I have to do > > > > # make -f Makefile.cvs > > # ./configure (+my prefix) > > # make > > # make install > > > > every time? > > Or is it already done with "svn up digkam"? > > No 'svn up' is just updating/downloading the sources. Makefile.cvs and > configure you only have to do when a Makefile.am was in the updated files. not only Gerhard, also when a new file based on QObject have been added on repository. In this case, if you don't rebuild the Makefile relevant of new QObject implementation, you will have an error about a '.moc' file missing ! You can use 'make force-reedit' in local where the QObject implementation based have been added instead to rebuild all makefiles to solve the problem... but if you have a fast computer, this is not a problem to process all Makefiles at the same time (:=))) Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |