[cmake-developers] [CMake 0012245]: Watcom WLIB Needs case sensitive option

2011-06-04 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12245 == Reported By:d3x0r Assigned To:

[cmake-developers] Getting some stuff from KDE into cmake

2011-06-04 Thread Alexander Neundorf
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

[cmake-developers] Automoc in cmake

2011-06-04 Thread Alexander Neundorf
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

[cmake-developers] Adding argument OPTIONAL to find_package() and add_subdirectory

2011-06-04 Thread Alexander Neundorf
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

[cmake-developers] [CMake 0012246]: CMake NMake generator /machine defect

2011-06-04 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://www.vtk.org/Bug/view.php?id=12246 == Reported By:Thomas Laguzzi Assigned To:

[cmake-developers] Creating a separate project/package which provides cmake extensions/modules

2011-06-04 Thread Alexander Neundorf
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

Re: [cmake-developers] Creating a separate project/package which provides cmake extensions/modules

2011-06-04 Thread Nicolas Desprès
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:

Re: [cmake-developers] Automoc in cmake

2011-06-04 Thread Nicolas Desprès
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

[cmake-developers] Making _IMPORT_PREFIX from an installed exports-file available to an including file

2011-06-04 Thread Alexander Neundorf
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