Dear digiKam website maintainer,
I hope you read on this mailing list or someone forwards my message to you. On the digiKam website I could not find out who is responsible for the site itself, but that is not what this message is about. It is about the very important "download" section, more precisely about the "second choice", "compile a tarball". I'm writing this because of the trouble I have with the current "beta" tarballs. Looking at digiKam's release history, with many betas in short sequence, followed by "release candidates" it seems obvious that betas are a lot less well-tested and stable than non-beta versions. But that is not the case with every open-source project (e.g. mplayer, if I'm not mistaken), and the blog-like structure of the website very much highlights the current beta release. So I suggest putting more emphasise on the stable version by changing a few sentences on the tarball page: http://www.digikam.org/drupal/download?q=download/tarball old: "Installing a tarball will get you the most up-to-date stable version of digiKam. But it can happen that you run into all kinds of problems related to compiling." new: "Installing a tarball will get your the most up-to-date stable or beta version of digiKam. But it can happen that you run into all kinds of problems related to compiling, especially with beta versions." Isn't the "set of commands" to compile digiKam somewhat outdated, too? Currently it says: ./configure --prefix=/usr make su -c "make install" I'd change that to: cmake . make make install One should add the sentence "Make sure you have appropriate rights for the last step", or similar. Vlado _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hi there,
I took another approach on building digikam on OS X. This time I tried building from svn, as I don't full understand which version gets fetched with the selfcreated portfile for macports. After having all the dependencies installed via macports, I followed the instructions on the website. The cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=`kde4- config --prefix` ../../kdegraphics line failed cause in the file /opt/local/share/apps/cmake/modules/ FindPhonon.cmake there was a search path for the phonon headers which pointed to "$ {PHONON_INCLUDE_DIR}/phonon/phononnamespace.h" instead of "${PHONON_INCLUDE_DIR}/Headers/phononnamespace.h". After a small edit the cmake run went fine. But compilation stopped forcefully after 23%. [ 23%] Building CXX object digikam/digikam/CMakeFiles/ digikamdatabase.dir/__/libs/threadimageio/pgfutils.o Linking CXX shared library ../../lib/libdigikamdatabase.dylib ld: warning can't open dynamic library: Qt3Support.framework/Versions/ 4/Qt3Support referenced from: ../../lib/libdigikamcore.1.0.0.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2) Has anyone encountered that error before? As this is no 3rd party tool but the digikam core itself, I think this is not a missing dependency. I have checked and found the file mentioned under /Library/Frameworks/ Qt3Support.framework/Versions/4/Qt3Support. Any idea why it is not found while compiling? Thanks Stefan _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |