The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12245
==
Reported By:d3x0r
Assigned To:
Hi,
I'm currently at the KDE Platform Sprint, where we (a bunch of KDE developers)
are discussing how to move on with the KDE platform.
This includes some things regarding cmake.
When we introduced cmake in KDE, there were not that many other free projects
using cmake, so our cmake extensions
Hi,
one feature which all KDE developers are used to and which is also used by
qmake when building Qt is automoc.
This means that you don't have to write
qt4_wrap_cpp(srcs ${filesToBeMoced})
but instead you simply do
kde4_add_executable(hello ${srcs})
and everything including moc is handled
Hi,
again from the KDE sprint...
1) We have a macro
macro_optional_find_package().
The purpose is to be able to build without a specific package even if that
package is installed and would actually be found by the find_package() call.
Basically this is a wrapper around find_package(), but
The following issue has been SUBMITTED.
==
http://www.vtk.org/Bug/view.php?id=12246
==
Reported By:Thomas Laguzzi
Assigned To:
Hi,
again from the KDE sprint...
We have around 150 cmake modules in kdelibs...
Several libraries are not before kdelibs, so they don't have access to
those.
So, what we came up with is that create a new package which just contains our
cmake modules, so they can be used by non-KDE
Hi,
Sounds reasonable to me. It reminds me th autoconf archive project.
Also, I have always been doing the same: keep my cmake modules in a
separate repository which is added as a submodule in all my others
projects.
-Nico
On Saturday, June 4, 2011, Alexander Neundorf neund...@kde.org wrote:
Hi,
IMHO, both proposals are too Qt/KDE specific to be integrated into
cmake this way. Maybe cmake could provide a more generic approach
like allowing you to run whatever dependency scanner at some stage in
the build process.
-Nico
On Saturday, June 4, 2011, Alexander Neundorf neund...@kde.org
Hi,
when installing an export-file cmake has the nice feature to calculate the
CMAKE_INSTALL_PREFIX from the current location:
-8--8--8
# Compute the installation prefix relative to this file.
GET_FILENAME_COMPONENT(_IMPORT_PREFIX