Re: building

[James B. <jb...@uc...>]

I just rsynced Qt3 (and it hasn't changed for a while, which means it 
stabilizing == good) and built everything, including check.  I did not have 
change KDE_OPTIONS or any other system variables.  

Some background information: for the regular kde cvs build I have 
/usr/local/qt symlinked to /usr/src/kde-cvs/qt-copy.  The rsynced version of 
Qt3 is in /usr/src/qt3, and is built but *not* "make install"ed. Configure 
options were: "-prefix /usr/src/qt3 -debug -qt-gif  -no-g++-exceptions 
-system-jpeg -no-tablet".  Both qt directories are in ld.so.conf, but QTDIR 
points to qt2.

Steps to compile kjabber:
./configure --enable-debug --with-qt-dir=/usr/src/qt3
make
## this gives you the error: 
## roster_meta_unload.cpp:5: `objectDict' ## undeclared
## open test_roster_meta_unload.cpp, insert the line 
## "Q_EXPORT QObjectDictionary *objectDict;"
make
make check
## this gives you the error: 
## test_roster_meta_unload.cpp:5: `objectDict' ## undeclared
## open test_roster_meta_unload.cpp, insert the line 
## "Q_EXPORT QObjectDictionary *objectDict;"
make check

The only warning this build gives is when running test-roster: "/usr/bin/ld: 
warning: libqt.so.2, needed by /usr/local/kde/lib/libDCOP.so, may conflict 
with libqt.so.3".  Since we don't use DCOP, I don't think this is a problem, 
and it will go away with the qt3 conversion anyway.

The final class, kjabber, I cannot compile yet because of inheritence 
problems; kextsock is derived from qt2's qsocket, and I mix in qt3's qsocket. 
 For the most part, however, this class is coded.  After this is tested, the 
next steps are intergrating it in the rest of kit2 (which shouldn't be much 
trouble as the API hasn't changed much), converting plugins and such to use 
kjabber's packet types, then adding more robust support for things like 
vcards, agents, encryptino, and other advanced jabber features.  After that I 
have some new ideas about plugins, but that is a long way off.

I don't see much happening until kde3 (cvs HEAD) becomes compilable 
regularly, both becuase this is important, and I will be busy with the start 
of school until then.  Cheers,

-- 
Jim Blomo   	<Bla...@yi...>
		<jb...@uc...>

Lazy programmers are the best programmers. Think Tom Sawyer painting the 
fence. That's intelligence.
					-Linus Torvalds
search.keyserver.net