Hi all,

Since all the other kids in the block are doing it, I felt I had to try 
CMake[1] (replacement for autotools). So I have created the qt-gui_cmake 
branch for this purpose. Since it now works for me, I would like to ask the 
rest of you to try it out and let me know what you think.

HOWTO
=====
1. Check out the branch to licq/plugins
licq/plugins # svn co http://svn.licq.org/svn/branches/qt-gui_cmake

2. Create the dir where you will be building qt-gui. It is highly recommended 
not to build directly in the source tree.
licq/plugins # mkdir qt-gui_cmake/build && cd qt-gui_cmake/build

3. Run "configure". For kde support:
build # cmake -DWITH_KDE=1 ..
(Note the two dots at the end. That is the path to the source.)

If you don't want kde, leave out -DWITH_KDE=1. To build with debug support, 
add -DCMAKE_BUILD_TYPE=debug. That's it! If you'd like to change some 
variable you can either use -DVAR=VALUE or run ccmake.
build # ccmake .
(Note the dot!)

4. Build it!
build # make
(make VERBOSE=1 gives more output)


NUMBERS
=======
My biggest problem with autotools (once you actually get it to work) is that 
it's takes a looooong time to go from a freshly checked out copy to one 
that's ready to build. That's pretty annoying when you're trying to fix the 
build system.

# time (make -f Makefile.cvs && ./configure --with-kde)
real    0m35.253s
user    0m20.595s
sys     0m5.660s

# time cmake -DWITH_KDE=1 ..
real    0m4.485s
user    0m1.962s
sys     0m0.665s

Even if the test is not completely fair (configure checks for gpgme and a few 
additional tools that cmake currently doesn't), the numbers still speak for 
themselves.


TODO
====
The branch is not yet as complete as the autotools one.
- make install only installs the library
- the plugin is prefixed with lib so you have to use -p 
full/path/to/liblicq_kde_gui.so when starting licq
- doesn't check for lrelease/lupdate (needed for locales)
- doesn't check for GPGME
- probably some more stuff here

What I'm interesting in hearing is: Does it build for you?

// Erik

[1] - http://www.cmake.org/

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

Erik Johansson
http://ejohansson.se

Attachment: pgprfmJpPZWEo.pgp
Description: PGP signature

Reply via email to