location of default KDE installation folder

Dimension User · 06-11-2005, 04:49 PM

Hi. I'm trying to install digiKam 0.72 ( from digikam-0.7.2.tar.bz2) from source in FC3, and I'm stuck on the README instructions:

1) export WANT_AUTOCONF_2_5=1
2) export KDEDIR=KDE_installation_dir_on_your_system
3) if you are installing libkipi/libkexif in a non-standard location
let pkg-config know about their paths:
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/path/to/installation/lib/pkgconfig
4) make -f Makefile.cvs
5) ./configure
6) make
7) su
8) make install

export KDEDIR=KDE_installation_dir_on_your_system I'm guessing that this means I should replace KDE_installation_dir_on_your_system with the actual directory, but I don't know where that is. I searched for all KDE files and folders on my system, but I couldn't find any that specifically say "KDE install." Could someone please tell me where it is?

Also, what are the export WANT_AUTOCONF_2_5=1 and make -f Makefile.cvs lines for? In all other source installs I've done, I started with ./configure and went right through to make install.

I didn't see these special instructions before I simply typed ./configure and got a message saying that I needed imlib2, which I've since installed. After I get all this info, and type the first four steps, do I type ./configure again?

reddazz · 06-12-2005, 02:19 AM

Do the following,

Code:

$make -f Makefile.cvs
$./configure --prefix=`kde-config --prefix`
$make
#make install

The --prefix=`kde-config --prefix` part tells the configure script to search for the KDE installation prefix and use that as the prefix for whatever you are trying to install.

Dimension User · 06-12-2005, 02:55 PM

Hello, reddazz.

Thanks for once again coming to my rescue. I just have one question; it looks like the ./configure --prefix=`kde-config --prefix` line takes care of the second step in the instructions (export KDEDIR=KDE_installation_dir_on_your_system), but what about the first step (export WANT_AUTOCONF_2_5=1)?

reddazz · 06-12-2005, 03:24 PM

I am not sure about that one. I think if you have autoconf 2.5.1 this should already be set so you won't need to export anything, but if not just do "export WANT_AUTOCONF_2_5=1" before doing "make -f makefile.cvs".

Dimension User · 06-12-2005, 03:50 PM

Shoot. I got a strange error. I opened the terminal and typed "su -" to get root permissions, navigated to the digiKam folder, and because my version of autoconf is apparently 2.59 I typed "export WANT_AUTOCONF_2_5=1". Then I typed "make -f Makefile.cvs". I got back
"make: Makefile.cvs: No such file or directory
make: *** No rule to make target `Makefile.cvs'. Stop."
What did I do wrong?

reddazz · 06-12-2005, 04:26 PM

If you already have a configure script you don't need to do "make -f Makefile.cvs", so it may not exist. Try going straight to doing "./configure".

jschiwal · 06-12-2005, 04:46 PM

Use "su" before the make install step. I had an error once because a file needed was in a normal users path but not in root's path. I had used "su -" before the make install step, which was the source of the error.

Dimension User · 06-22-2005, 06:00 PM

Sorry it took me so long to reply! I've been so busy that I haven't had time to try installing digiKam again until today.

I got another error

configure: error: expected an absolute directory name for --prefix: kde-config –prefix

Don't worry about it, though; I'm going to upgrade to FC4 soon, and I think it has digiKam already, so I'm giving up for now. I think the digiKam developers could be a little more specific with their installation instructions, though.

Quote:

Use "su" before the make install step. I had an error once because a file needed was in a normal users path but not in root's path. I had used "su -" before the make install step, which was the source of the error.

That's a great tip, jschiwal. I had been using only “su,” until I read that “su -” gave you true root power. I forgot that would also change path info.

When is it better to use “su” vs. “su -”?

P.S. When I got the above error, I tried it both ways but got the same message each time.