Compiling Issues (my version of the wheel)
Locked
12
12
Compiling Issues (my version of the wheel)
 
|
Thank-you everybody, for not taking too much offense at my rant. I can see where "Newbie Fatigue" can get quite frustrating for those of you who find this to be a second nature piece of cake. Yes, it will probably do us good to experience similar wounds as the experts had when they jumped through the same flaming barbed wire hoops . The problem for many of us Newbs is that because we don't come from the same Computer World, our wounds can be quite fatal since we don't even know which hoops to jump through. If we're lucky enough we can continue to scour the internet, pickling up bits and pieces of instructions, here and there. Unfortunately, many times, the information is conflicting and we end up in a pit somewhere, unable to climb out and left calling for help.
My problem during my most-recent journey was finding all of the right dependencies. The instructions on the digiKam site were not very clear on this. Yes, links to other relevant pages and text files were there, but there wasn't a single source where all of this information was then aggregated for final consumption. This left me guessing at what I had to do next. Even if some of the dependencies that I uncovered were correct versions, I had no idea where to install them. I think that rather than relating all of the steps along the often-tortuous path that we've taken before finally falling into the pit, it would be so much easier if, right from the start, we had a concise "master map" to follow. Then, if we do something stupid, it would probably be much less frustrating (!) for those volunteers who have successfully navigated these pitfalls to pull us through the rest of the way. I think that I've finally found such a detailed map: http://www.digikam.org/drupal/download/SvnAlongStable (thank you very much, Mike Hansen!). Since this is Ubuntu-specific rather than the Fedora instructions graciously provided earlier by Christian (thanks again Christian!), I should be able follow it a little easier. I'll go along, step-by-step, and see where it takes me. Hopefully I won't have to bother you all again. * I now understand that a big part of the problem is Ubuntu's glacial pace at providing updated packages. I also understand that this is why it's necessary to "roll one's own" from a number of individual sources. What I don't understand is why everybody is forced to do this, thus reinventing the wheel. Why, along with the source files, isn't there an option to simply download and install a single tarball with everything already included? Yeah, it's a weanie desire not to want to slog through the quagmire that the initial inventor traversed but, it sure would make life much simpler  Happy Holidays! _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Compiling Issues (my version of the wheel)
|
|
Re: Compiling Issues (my version of the wheel)
|
|
Re: Compiling Issues (my version of the wheel)
|
|
Re: Compiling Issues (my version of the wheel)
|
|
In reply to this post by Mark Greenwood
Thanks Mark. Been there, done that
 . I was able to successfully install digiKam 1.6.0 from this very PPA a few days ago. The problem is that exiv2 2.1 isn't included. Thus, apparently my only recourse is to build my own. On Sun, 2010-12-19 at 17:36 +0000, Mark Greenwood wrote: On Sunday 19 Dec 2010 17:06:08 Hevï Guy wrote: > Thank-you everybody, for not taking too much offense at my rant. I can > see where "Newbie Fatigue" can get quite frustrating for those of you > who find this to be a second nature piece of cake. Yes, it will probably > do us good to experience similar wounds as the experts had when they > jumped through the same flaming barbed wire hoops . The problem for many > of us Newbs is that because we don't come from the same Computer World, > our wounds can be quite fatal since we don't even know which hoops to > jump through. If we're lucky enough we can continue to scour the > internet, pickling up bits and pieces of instructions, here and there. > Unfortunately, many times, the information is conflicting and we end up > in a pit somewhere, unable to climb out and left calling for help. > > My problem during my most-recent journey was finding all of the right > dependencies. The instructions on the digiKam site were not very clear > on this. Yes, links to other relevant pages and text files were there, > but there wasn't a single source where all of this information was then > aggregated for final consumption. This left me guessing at what I had to > do next. Even if some of the dependencies that I uncovered were correct > versions, I had no idea where to install them. I think that rather than > relating all of the steps along the often-tortuous path that we've taken > before finally falling into the pit, it would be so much easier if, > right from the start, we had a concise "master map" to follow. Then, if > we do something stupid, it would probably be much less frustrating (!) > for those volunteers who have successfully navigated these pitfalls to > pull us through the rest of the way. > > I think that I've finally found such a detailed map: > http://www.digikam.org/drupal/download/SvnAlongStable (thank you very > much, Mike Hansen!). Since this is Ubuntu-specific rather than the > Fedora instructions graciously provided earlier by Christian (thanks > again Christian!), I should be able follow it a little easier. I'll go > along, step-by-step, and see where it takes me. Hopefully I won't have > to bother you all again. > > * I now understand that a big part of the problem is Ubuntu's glacial > pace at providing updated packages. I also understand that this is why > it's necessary to "roll one's own" from a number of individual sources. > What I don't understand is why everybody is forced to do this, thus > reinventing the wheel. Why, along with the source files, isn't there an > option to simply download and install a single tarball with everything > already included? Yeah, it's a weanie desire not to want to slog through > the quagmire that the initial inventor traversed but, it sure would make > life much simpler ;-) Some hints for Ubuntu users: sudo apt-get build-dep digikam (installs all dependencies for building digikam) apt-get source digikam (gets the source code for the ubuntu digikam package - easiest thing to do if all you want to do is rebuild it against a new library) dpkg-buildpackage -rfakeroot -uc -b (builds the .deb package from the source you just retrieved) sudo add-apt-repository ppa:philip5/extra sudo apt-get update sudo apt-get upgrade (sets up a repository with, amongst other things, the latest and greatest digikam and kipi-plugins) All found via Google. Happy holidays ;-) Mark > > Happy Holidays! > _______________________________________________ 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 |
Re: Compiling Issues (my version of the wheel)
|
|
Re: Compiling Issues (my version of the wheel)
|
|
Re: Compiling Issues (still no joy)
|
|
In reply to this post by Photonoxx
In spite of not hearing back from somebody I went ahead and followed these guidelines. At the conclusion of the incredibly longggg build, I opened digiKam and looked at the components. Damn; that infuriatingly buggy exiv2 1.9 was still there
 Has anybody else got a suggestion or, is everybody tired of this. I know that I am but, I've got no choice but to go on if I have any hope of getting this program to operate properly. I suppose that I can always boot back into Windoze and run Adobe Bridge, eh? Grrrrr.... I'm sure that there must be a perfectly logical reason for it but, I still don't understand why there isn't a simple deb available with all of the necessary stuff. I mean it the humblest manner possible when I ask why must everybody have to reinvent the wheel?? It may be fun to some but, for those of us who aren't programmers by trade but are mere butchers, bakers and candle stick makers, it ranks up there with going to the dentist in terms of pleasure factor. On Mon, 2010-12-20 at 16:33 +0100, Photonoxx wrote: Le Sun, 19 Dec 2010 18:36:53 +0100, Mark Greenwood <[hidden email]> a écrit: > Some hints for Ubuntu users: > > sudo apt-get build-dep digikam (installs all dependencies for building > digikam) > > apt-get source digikam (gets the source code for the ubuntu digikam > package - easiest thing to do if all you want to do is rebuild it > against a new library) > dpkg-buildpackage -rfakeroot -uc -b (builds the .deb package from the > source you just retrieved) > > sudo add-apt-repository ppa:philip5/extra > sudo apt-get update > sudo apt-get upgrade (sets up a repository with, amongst other > things, the latest and greatest digikam and kipi-plugins) > > All found via Google. Happy holidays ;-) Can you confirm you post here two different hint (the one with dpkg-buildpackage and the other with PPA). Inspired by this, I found way simpler way two get evix2 0.20 working with Digikam. At least you have to pass by a compile step, but don't have to compile Digikam. May be it's a little late for Hevï Guy... If more technician could validate this method, it would be nice. First of all I download exiv2 deb packages from natty repository on Launchpad. I think the needed packages are mostly Libexiv2-9 and libexiv2-dev https://launchpad.net/ubuntu/natty/+package/libexiv2-9 https://launchpad.net/ubuntu/natty/+package/libexiv2-dev For each URL you still have to select which published version you need (32bits or 64bits ?) and click on the deb link in the new page (under "downloadable item...") With this deb you can install Libexiv2-9 and libexiv2-dev After that, you just have to recompile you libkexiv2-8 that is used by Digikam. To do that, I make this in an appropriate folder for exemple src: mkdir src cd src sudo apt-get build-dep libkexiv2-8 apt-get source libkexiv2-8 cd kdegraphics[you-version, just look the name of the created folder] dpkg-buildpackage -rfakeroot -uc -b This last command take a quite long time because I don't knows how to only generate the deb for libkexiv2, and the command line generate packages for all the kdegraphics components. but at the end, in the src directory, you'll get all the generated deb files. Now, there just stay to install libkexiv2-8[your-version].deb file. Double-clicking on it to open software-center give me some trouble. In fact, when I click on "reinstall" button, Software-center says Digikam and some other software have to be uninstalled to reinstall libkexiv2-8 package, and so, I decided to install gdebi software and Just have to make a right click on libkexiv2-8.*.*.deb and choosing "open with gdebi...", and reinstall work without alert. Launching Digikam give me now exiv 0.20 in component info. If someone, more expert than me, could confirm there's no matter with this way... _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Compiling Issues (The Eagle has landed!!!)
|
|
Woo hoo!
Since I understand Frenglish as well as I understand Linux ( I say that with all due respect, Nicolas!) I wasn't able to immediately understand that I had to go into the src directory and install the libexiv deb. Eventually, this is exactly what I did. Nicolas, you are a saviour: digiKam is now running with exiv2 .20 ! Merci, merci, merci! As soon as I wash the blood and gore from myself, set my bones and and suture the wounds, I'll be able to get back out there and take pictures again with my fine D90. Then, hopefully, I won't have to wait 3 moon phases before each download is processed in digiKam as I initially did. * A great big Thanks to everybody else too, including Michael Hansen, Gert Kello, Christian ? and Mark Greenwood  On Mon, 2010-12-20 at 16:19 -0600, Hevï Guy wrote: In spite of not hearing back from somebody I went ahead and followed these guidelines. At the conclusion of the incredibly longggg build, I opened digiKam and looked at the components. Damn; that infuriatingly buggy exiv2 1.9 was still there _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Compiling Issues (still no joy)
|
|
Re: Compiling Issues (still no joy)
|
|
Re: Compiling Issues (still no joy)
|
|
Re: Compiling Issues (The Eagle has landed!!!)
|
|
Re: Compiling Issues (The Eagle has landed!!!)
|
|
Re: Compiling Issues (still no joy)
|
|
In reply to this post by Mark Greenwood
On Tue, 2010-12-21 at 10:53 +0000, Mark Greenwood wrote: With respect, it's abundantly clear to anybody who does some research before comitting to a platform to work on. In this specific case, a quick Google of 'Digikam Nikon D90 Ubuntu' brought up plenty of references to the speed problem. Even the most knowledge-less newbie could have drawn some conclusions from that - like maybe not to bother trying Ubuntu. I don't know about others but, I certainly didn't forsake widoze for Ubuntu just because I knew digiKam was available here. Discovering the program *after* arriving here was a very pleasant surprise. Here's a Newb perspective:> That's when users face problems like this, which they aren't qualified to solve, and wouldn't have got involved with if they suspected what was coming. I don't mean to sound rude. We make our own decisions and we should make sure they are informed ones, then we won't find ourselves moaning about how things weren't made clear to us. Some of us are willing to enter into situations which we know are chock full of evil monsters if we also know that there is a worthwhile reward waiting for us at the end. After using digiKam with my simple Point'n'Shoot, I became very impressed by its capabilities. It was only when I finally purchased my Nikon DSLR that I encountered the infuriating exiv2-related problems. Learning that others had successfully overcome these issues was my light at the end of the tunnel. The "moaning" was the result of feeling quite alone in a world where I was unable to speak the language of its residents. I'm sure that the frustration was a two-way street. .With the help of some very generous people here, I was finally able to sort it out. I suppose that I also find "moaning" to be distasteful. There are a great many proficient Linux users who, I am convinced, feel that this is no place at all for Windoze- refugee Newbs. I often see such moaning in response to very-basic-to-you but major-to-us questions. Indeed, often the responses are disdainful and sometimes even rude. It seems that the only reason for them to even reply to a question is to throw their superiority into the face of the under dogs Luckily, just like in any society, those bullies rank in the minority. Thank-you again to everybody who showed patience and understanding during this process 
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Compiling Issues (still no joy)
|
|
Clean reinstall of Ubuntu 10.10 = Digikam with exiv2 .19 ARRRGGGGHHHH...!
|
|
Re: Clean reinstall of Ubuntu 10.10 = Digikam with exiv2 .19 ARRRGGGGHHHH...!
|
|
Re: Clean reinstall of Ubuntu 10.10 = Digikam with exiv2 .19 ARRRGGGGHHHH...!
|
|
Re: Clean reinstall of Ubuntu 10.10 = Digikam with exiv2 .19 ARRRGGGGHHHH...!
|
|
| Free forum by Nabble | Edit this page |