Moving 3.5 development into branches/KDE/3.5
neundorf at kde.org
Thu Jun 2 00:26:16 BST 2005
On Wednesday 01 June 2005 03:36, Benjamin Meyer wrote:
> Speaking of which the previous thread on the build system kinda tottered
> out. Has anyone else had a chance to play around with all of the different
> tools mentioned to provide more feedback on the topic?
> -Benjamin Meyer
kdevelop should compile with cmake (from cvs).
It would be nice if you could try how it works on OS X.
It probably needs some tuning in KDE_TARGET_LINK_CONV_LIBRARIES() and maybe
some other minor issues.
It's a first try and can be improved a lot. Most configure checks are missing.
Various things can probably further be simplified with some macros.
-the libs compile, the parts compile, kdevelop compiles and links
-fake libtool .la files for the parts are generated
-install rules for most things exist
-uic and dcop stuff is handled
CMake: One tool to build them all: no autoconf, no automake, no libtool, no
m4, no perl, no python, no shell, only pure cmake
Work: alexander.neundorf at jenoptik.com - http://www.jenoptik-los.de
Home: neundorf at kde.org - http://www.kde.org
alex at neundorf.net - http://www.neundorf.net
More information about the kde-core-devel