-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay, I just composed a long ranting email about how kpilot won't compile.  
Then, I deleted it.  I'm now replacing it with this email, which is basically 
a "fair warning".  If you want to compile kpilot from cvs, these are the 
steps.

1. goto your programming directory
2. cvs co -r  KDE_2_2_BRANCH kdepim
3. rm -fR kdepim/kpilot
4. cvs co kdepim/kpilot
5. cd kdepim && make -f Makefile.cvs
6. ./configure --with-extra-includes=/usr/lib/libpisock  	#extra-includes is 	
	optional and depends on your distribution.  mine is debian
7. cd kpilot/lib && make
8. cd .. && make

At that point, you should have a working compile and you can go to town...  
The kicker is making sure to seperately run make in the lib directory, as the 
automatically generated makefile does *not* run it for you.  That could be 
considered a bad thing :-)

Also, I tried modifiying the "Makefile-standalone" and using it,as is my 
wont, and it refuses to do anything, replying with: "No rule to make target 
`uiDialog.moc', needed by `kpilotConfig'.  Stop."  This could also be 
considered a bad thing.....

Hope that helps someone....
  
- -- 
D.A.Bishop
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7xiesKEJ4huP2XBERAiBEAJ4uqFMg1vXPS3YhgEsKNOYbbttTSACgqWCl
cuROHqD/E2qILOMY99buxdg=
=r68d
-----END PGP SIGNATURE-----
_______________________________________________
Kde-pim mailing list
Kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim