Thanks to you all.
Robert Comtois
If you wish to reach me directly use the folling address w/o the spaces.
Bob . Comtois @ Laposte . net
And where did you get it from? What does the author say about it? When
was it written? Is it
http://devel-home.kde.org/~kdiskcat/
??
The KDE disk-catalog (C) 1998-2000 Bala'zs Tere'nyi
This page is maintained by the author.
Any suggestions, bug reports, patches are wellcome!
0.1 1999.05.28. 155313 kdiskcat-0.1.tar.gz
0.3 1999.08.24. 182829 kdiskcat-0.3.tar.gz
0.3.1 1999.08.29. 183301 kdiskcat-0.3.1.tar.gz
0.4 1999.10.19. 190204 kdiskcat-0.4.tar.gz
0.5 2000.02.10 205151 kdiskcat-0.5.tar.gz
0.5.1 2000.03.22 214967 kdiskcat-0.5.1.tar.gz
0.5.2 2000.04.12 221949 kdiskcat-0.5.2.tar.gz
0.5.3 2000.05.02 222067 kdiskcat-0.5.3.tar.gz
Looks old to me!
> I first unpacked the file, the I put everything in a sub-directory
> (Kdiskcat).
> Next I read the instructions.
Oooh. Dangerous!
> Then I ./configure while I was in the Kdiskcat directory under SU.
Why? You should NOT run as root.
> After a few lines of "checking" , the compiling stopped with the
> following line:
> "checking for Qt... configure: error: Qt-1.4 (headers and libraries) not
OK, so you know what you need to install.
> found. Please check your installation!"
> So I searched the web.
Why? Doesn't your distro provide libqt-1.4 or better?
> From: rpm -qa | grep qt I get:
> libqt3-devel-3.1.1-13mdk
Doesn't look likely. Isn't qt up to about version 3.something? 1.4 must
be years old! When was this package produced?
> libunixODBC2-qt-2.2.4-1mdk
other stuff.
> libqt3-3.1.1-13mdk
Yes, 3.something again.
> libqt3-common-3.1.1-13mdk
Ditto.
> unixODBC-gui-qt-2.2.4-1mdk
Other stuff.
> I admit I don't know what Qt-1.4 is.
Why don't you? It means what it says! It's the message produced by the
config script in response to a particular condition. If you want the
precise semantics, you only have to look at the script. If you want a
layman's rough approximation, it's "version 1.4 of the qt lib and
headers".
> What is the way to compile this program?
There is no "the way". You do it by porting the source forward to
work with your libraries and headers (shudder), or by finding the
development environment it was written for and reestablishing it, so
that the thing feels at home. Note that you may have to correct
compiler incompatibilities too.
> Please I realy don't know what to do next.
Why not? How does "talk to the author" grab you? He says
Any suggestions, bug reports, patches are wellcome!
and you have a bug report.
> ps. I'm running Mandrake linux 9.1 (power pack)
Tough.
BTW, for me it's quite happy with my qt installation:
checking for Qt... libraries /usr/lib/qt/lib, headers /usr/lib/qt/include
checking if Qt compiles without flags... yes
And I have libqt3.0.0.0-6 .
It fails for me on my kde:
checking for kde headers installed... configure: error: your system is
not able to compile a small KDE application!
Check, if you installed the KDE header files correctly.
And looking at the log, I see:
configure:3628: g++ -c -O2 -Wall -I/usr/lib/kde/include -I/usr/lib/qt/include -I/usr/X11R6/include conftest.C
conftest.C: In function `int main()':
conftest.C:7: no method `KApplication::kde_htmldir'
conftest.C:8: no method `KApplication::kde_appsdir'
conftest.C:9: no method `KApplication::kde_icondir'
conftest.C:10: no method `KApplication::kde_sounddir'
conftest.C:11: no method `KApplication::kde_datadir'
conftest.C:12: no method `KApplication::kde_localedir'
conftest.C:13: no method `KApplication::kde_cgidir'
conftest.C:14: no method `KApplication::kde_configdir'
conftest.C:15: no method `KApplication::kde_mimedir'
conftest.C:16: no method `KApplication::kde_toolbardir'
conftest.C:17: no method `KApplication::kde_wallpaperdir'
conftest.C:18: no method `KApplication::kde_bindir'
conftest.C:19: no method `KApplication::kde_partsdir'
So my KDE sources are just plain incompatible with what it expects to
see. My KApplication class is deficient from its point of view. Shrug,
Boohoo.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and
mail diffs or instructions to the address given in the `README' so
they can be considered for the next release. If at some point
`config.cache' contains results you don't want to keep, you may
remove or edit it.
Yuh. Shall I bother? I'll force it to be happy with my kde ... well,
the program they try is:
#include <stdio.h>
#include "confdefs.h"
#include "config.h.bot"
#include <kapp.h>
int main() {
printf("kde_htmldir=\\"%s\\"\n", KApplication::kde_htmldir().data());
printf("kde_appsdir=\\"%s\\"\n", KApplication::kde_appsdir().data());
printf("kde_icondir=\\"%s\\"\n", KApplication::kde_icondir().data());
printf("kde_sounddir=\\"%s\\"\n", KApplication::kde_sounddir().data());
printf("kde_datadir=\\"%s\\"\n", KApplication::kde_datadir().data());
printf("kde_locale=\\"%s\\"\n", KApplication::kde_localedir().data());
printf("kde_cgidir=\\"%s\\"\n", KApplication::kde_cgidir().data());
printf("kde_confdir=\\"%s\\"\n", KApplication::kde_configdir().data());
printf("kde_mimedir=\\"%s\\"\n", KApplication::kde_mimedir().data());
printf("kde_toolbardir=\\"%s\\"\n",
KApplication::kde_toolbardir().data());
printf("kde_wallpaperdir=\\"%s\\"\n",
KApplication::kde_wallpaperdir().data());
printf("kde_bindir=\\"%s\\"\n", KApplication::kde_bindir().data());
printf("kde_partsdir=\\"%s\\"\n", KApplication::kde_partsdir().data());
return 0;
}
which is kinda specific. Why doesn't my KApplication class have those
methods? Oh - I use kde2. Maybe I could try it with kde3 ... nah. No
dice. Let's read kapp.h ... I think it really wants kde 1.1. My
KApplication class is nothing like that. I'm not going to bother .. ask
the author.
Peter
Thanks again
Robert
Well, I don't know what a disk-cataloguer is. It says:
It stores the directory tree (filenames, sizes, dates) of the
scanned disks (cd-roms, floppys or anything you can mount into
the filesystem) in its own database. The disks are stored in user
defined categories. The database is browseable in a treeview and
listview based browser window. You can write your own description
for each file.
It has great search capabilities. You can search for files or
descriptions using wildcards or regular expression, using
date/time or size conditions. The conditions could be mixed. The
search results are displayed in a table in editable order.
Doesn't the standard "locate" do the job for you? Or if you want a tree
view, combine that with your normal gui file browser.
Peter
Unless it catalogues non-mounted, removeable disks? So you can look at
the contents of more than one removeable disk?
Cheers
Colin
--
----------------------------------------------------------------------
Colin Brough Colin....@blueyonder.invalid
(Replace .invalid with .co.uk to reply)
Put "linux kde cd cataloguer" into google ...
Peter
> Well, I don't know what a disk-cataloguer is.
It's simply a program that creates a data base on your hd of all the
removable media you own.
So whenever you're looking for a file wheter it be on a cd, a zip disk ,
a floppy or any other removable media, you search the db of the
cataloguer and find where your file is.
Very nice if you're in a rush to find a photocopy of a certain
transaction of some years ago or anything else.
Robert