Have just tried to install krecipes (using sqlite) and using the ./configure -with-qt-dir=DIR command.
Being new I don't quite know what they mean by where the 'root of qt is installed' thing is supposed to mean. Have been trying to find out but am getting more and more frustrated by the lack of plain English explanations available. I do think that I may have two main problems getting the friggin thing installed:
1. As mentioned above I may be incorrectly using the ./configure command
2. I may be missing a vital library. I don't know. The German mag I'm using says that I need the kdelibs3-devel-version.rpm. Am using Mandrake 10 Community and have no idea what this might be called. Went to mandrake website and was very disappointed. Big surprise there.

When I do get the ./configure thingy to work it's like this...
[austin@ krecipes]$ ./configure -with-qt-dir=/
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for kde-config... /usr/bin/kde-config
checking where to install... /usr (as returned by kde-config)
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking whether g++ supports -Wmissing-format-attribute... no
checking whether gcc supports -Wmissing-format-attribute... yes
checking whether g++ supports -Wundef... no
checking whether g++ supports -Wno-long-long... no
checking whether g++ supports -Wnon-virtual-dtor... no
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
[austin@ krecipes]$

Any Ideas or suggestions (short of me throwing myself off a cliff)?

Cheers

well, check the config.log and see what the specific error was

also, i doubt the root of qt is in /, so you are best off just leaving off that flag and let configure automatically find it; only if it is not found should you directly specify its location (granted qt is installed)

also, this config problem doesn't seem to be related to the qt option....

I'm a develoer for Krecipes and this problem isn't at all related to Krecipes. It looks like you need to install the C++ compiler (g++).

You may have more dependencies once you get past this step. I'm more than happy to help you solve those.

And as TheOneAndOnlySM said, you don't need to worry about --with-qt-dir. I'll detects it automatically on Mandrake 10.

-Jason K

Thanks to both of you. It worked!

Only thing is that I think krecipes has a bit of a bug. When I select the krecipes handbook from the help menu, I get the KDE handbook. Am I missing something (again!)?

Anyway, on to solving the sound problem (no CD playback) so am off to another forum.

CHEERS!

Well, the handbook issue isn't exactly a bug, we just haven't gotten around to writing the help. We've been very busy programming and getting the program into a stable, fully-featured state. The help will have to wait awhile unless somebody else is willing to write it for us.

-Jason K