I seem to be having difficulty compiling from CVS... can anybody tell
me what the process is?
There's no makefile at the top. Tried make -f, as indicated on the
sourceforge site. That told me to get unsermake. Got it, tried the
same thing, the complaint is now that there is no configure.in.=20
There's a configure.in.in, but I don't know what do do with this.
Justin W. Hart
On Wednesday 29 March 2006 11:16, Justin Hart wrote:
> I seem to be having difficulty compiling from CVS... can anybody tell
> me what the process is?
Well, it's not that easy these days. To get our tiny app running, you
need unsermake (cmake soon), qt-copy from trunk/qt-copy,=20
branches/work/kdelibs4_snapshot (important: the snapshot, not=20
trunk/KDE/kdelibs), and trunk/KDE/kdepim.
for detailed instructions how to get it compiled and running. (It should be=
possible to compile kdepim just as described for kdebase and kdeutils).
If you have problems with compiling whole kdepim, you can just cd to the=20
following dirs and build them manually (after unsermake -f Makefile.cvs and=
configure on top-level):=20
libkmime, libemailfunctions, ktnef, libkcal, libkdepim, akregator=20
See http://akregator.pwsp.net/blog/ for a fancy dependency graph.
But be aware: it doesn't really work. It crashes. You can't do anything wit=
it but work on it (sounds attractive though, if you ask me).
If you want something working (boring, isn't it?), you can check out=20
branches/KDE/3.5/kdepim and compile that (needs nothing special but qt3-dev=
and kdelibs3-dev packages). Which is useful if you want to get the latest b=
fixes or help us to fix them.
If you run into problems with the KDE4/akregator compilation or if you have=
any other questions, just ask!