|
|
| (6 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| == A simple example ==
| | {{CMake/Template/Moved}} |
|
| |
|
| Let's just start with a simple example for an application, let's name it, well, kFoo. The CMakeLists.txt below gives the project a name, so that the project files for KDevelop/XCode/MSVC will have a good name. It will then find the KDE 4 installation on the system and setup the required include directories. The list of source files will be put into a variable named mySources, which will be automoced and then used to build an executable from it. The executable and its desktop file will finally be installed.
| | This page has moved [https://gitlab.kitware.com/cmake/community/wikis/doc/tutorials/How-To-Build-KDE4-Software here]. |
| <pre>
| |
| project(kfoo)
| |
| | |
| find_package(KDE4 REQUIRED)
| |
| | |
| include_directories( ${KDE4_INCLUDES} )
| |
| | |
| set(mySources main.cpp mywidget.cpp mypart.cpp)
| |
| | |
| kde4_automoc( ${mySources} )
| |
| | |
| kde4_add_executable(kfoo ${mySources})
| |
| | |
| target_link_libraries(kfoo ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )
| |
| | |
| install_targets( /bin kfoo)
| |
| install_files( ${XDG_APPS_DIR} FILES kfoo.desktop)
| |
| </pre>
| |
| | |
| == A full-featured example ==
| |
| | |
| Ok, and now for a full-featured but non-working example.
| |
| | |
| Give the project a name, find KDE 4 and setup CMAKE_MODULE_PATH. This has the effect that cmake will also use check the ${CMAKE_SOURCE_DIR}/cmake directory for files if you use include(somefile) or find_package(something). Please note that this directory is added to the former contents of CMAKE_MODULE_PATH. This is important, since if find_package(KDE4) was successfully, it will have setup CMAKE_MODULE_PATH so that it points to the directory where the cmake files installed with kdelibs are located.
| |
| <pre>
| |
| project(kfoo)
| |
| | |
| find_package(KDE4 REQUIRED)
| |
| | |
| set(CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake ${CMAKE_MODULE_PATH})
| |
| </pre>
| |
| | |
| Then apply the required settings:
| |
| <pre>
| |
| include_directories( ${KDE4_INCLUDE_DIRS})
| |
| add_definitions( ${KDE4_DEFINITIONS} )
| |
| </pre>
| |
| | |
| Create a variable which holds your source files:
| |
| <pre>
| |
| set(kfooSources main.cpp myappl.cpp view.cpp)
| |
| </pre>
| |
| | |
| If you have Qt designer ui files version 3 or 4 add them to the variable we just created:
| |
| <pre>
| |
| kde4_add_ui_files( kfooSources maindialog.ui logindialog.ui)
| |
| | |
| kde4_add_ui3_files( kfooSources printerdlg.ui previewdlg.ui)
| |
| </pre>
| |
| | |
| If you have files for the kconfig_compiler add them this way:
| |
| <pre>
| |
| kde4_add_kcfg_files( kfooSources settings.kcfg )
| |
| </pre>
| |
| | |
| | |
| You have some DCOP stuff too ?
| |
| I guess you already almost guessed it:
| |
| <pre>
| |
| kde4_add_dcop_skels(kfooSources someinterface.h anotherinterface.h)
| |
| | |
| kde4_add_dcop_stubs(kfooSources blah.h blub.h)
| |
| </pre>
| |
| So, if you have listed everything, you probably want automoc:
| |
| <pre>
| |
| kde4_automoc( ${kfooSources} )
| |
| </pre>
| |
| | |
| Please note that kde4_automoc() doesn't take the name of a variable as argument, but just a list of files. That's why kfooSource is "dereferenced" here.
| |
| | |
| Finally, tell cmake what you want to build:
| |
| <pre>
| |
| kde4_add_executable(kfoo ${kfooSources} )
| |
| </pre>
| |
| | |
| This is a slightly extended version of the original cmake add_executable().
| |
| Additionally it does some more RPATH handling and supports KDE4_ENABLE_FINAL.
| |
| Just as add_executable() the first argument is the name of the executable followed by the list of source files.
| |
| If you want to create a library instead of an executable, it works similar:
| |
| <pre>
| |
| kde4_add_library(kfoo ${kfooSources} )
| |
| set_target_properties( kfoo PROPERTIES VERSION 5.0.0 SOVERSION 5 )
| |
| </pre>
| |
| As above with add_executable(), kde4_add_library() is an extended version of the add_library() command. It adds support for KDE4_ENABLE_FINAL and under windows it adds "-DMAKE_KFOO_LIB" to the compile flags.
| |
| The set_target_properties() command is optional, if you don't need a version number for the library you can just skip it.
| |
| | |
| KDE is very modular, so if you want to create a KPart, or a control center module, or an ioslave, here's how to do it:
| |
| <pre>
| |
| kde4_add_plugin( kfoo ${kfooSources} )
| |
| </pre>
| |
| | |
| Now your application/library/plugin probably needs to link to some libraries. For this use the standard cmake target_link_libraries() command. For every KDE library there are variables in the form "KDE4_FOO_LIBS" available. Use them and you get also all depending libraries:
| |
| <pre>
| |
| target_link_libraries( kfoo ${KDE4_KDEUI_LIBS} ${KDE4_KIO_LIBS})
| |
| </pre>
| |
| | |
| | |
| And now some words about kdeinit-executables. They can also be created with cmake. Here's an example:
| |
| | |
| <pre>
| |
| kde4_add_kdeinit_executable(kbar ${kbarSources} )
| |
| target_link_libraries(kdeinit_kbar ${KDE4_KIO_LIBS} )
| |
| target_link_libraries( kbar kdeinit_kbar)
| |
| | |
| install_targets( /bin kbar)
| |
| install_targets( /lib kdeinit_kbar)
| |
| </pre>
| |
| | |
| As you can see, here's a bit more going on.
| |
| kde4_add_kdeinit_executable() creates both an executable with the given name and a library with the given name prefixed with "kdeinit_". Use target_link_libraries() to add all required libraries to the kdeinit_kbar library, and then link kbar against kdeinit_kbar.
| |
| | |
| In the examples above the install commands are missing. The KDE 4 support in cmake provides a bunch of predefined variables you should use, e.g. if it's a library:
| |
| <pre>
| |
| install_targets( ${LIB_INSTALL_DIR} kfoo)
| |
| </pre>
| |
| | |
| There is also PLUGIN_INSTALL_DIR and a bunch more variables, see the top of FindKDE4Internal.cmake for details.
| |
| | |
| == Where to find more information ==
| |
| | |
| The KDE 4 support of cmake consists of the file FindKDE4.cmake, which comes with cmake and is mainly a forwarder to the file FindKDE4Internal.cmake. In FindKDE4Internal.cmake system-dependent settings are set and the KDE libraries, executables and include directories reqauired for building KDE 4 software are searched. Additionally to FindKDE4Internal.cmake there are the files KDE4Macros.cmake. This file implements all the KDE4-specific commands we used above. If you do
| |
| <pre>
| |
| find_package(KDE4)
| |
| </pre>
| |
| these macros are automatically available to you.
| |
| There is also a file KDE4Defaults.cmake which sets some minor cmake options which are good, but not absolutely required for building KDE 4 software. If you want to use these settings, include this file:
| |
| <pre>
| |
| include(KDE4Defaults)
| |
| </pre>
| |
| These three files come with the KDE libraries and are installed to share/apps/cmake/modules/.
| |
| If you want to know more details, it is always a good idea to have a look at these files directly.
| |
| | |
| At the top of FindKDE4Internal.cmake you can find the complete documentation for all variables and macros these files provide.
| |
