Difference between revisions of "Development/Tools/Automoc4"

Jump to: navigation, search
(Usage)
Line 1: Line 1:
This wiki page will document automoc4.
+
==Usage in CMakeLists.txt==
 
+
You should not use the automoc4 executable directly. Instead use the FIND_PACKAGE()
==Usage==
+
command to use Automoc4 in your CMakeLists.txt (best use [http://websvn.kde.org/*checkout*/trunk/KDE/kdelibs/cmake/modules/FindAutomoc4.cmake FindAutomoc4.cmake]). Then you can add two lines per target to your CMakeLists.txt and you never need to worry about moc files anymore:
You should not use the automoc4 executable directly. Instead include the Automoc4Config.cmake file in your CMakeLists.txt (best use [http://websvn.kde.org/*checkout*/trunk/KDE/kdelibs/cmake/modules/FindAutomoc4.cmake FindAutomoc4.cmake]). Then you can add two lines per target to your CMakeLists.txt and you never need to worry about moc files anymore:
+
  
 
  set(foobar_srcs main.cpp foobar.cpp)
 
  set(foobar_srcs main.cpp foobar.cpp)
Line 8: Line 7:
  
 
then becomes
 
then becomes
 +
 +
find_package(Automoc4 REQUIRED)
  
 
  set(foobar_srcs main.cpp foobar.cpp)
 
  set(foobar_srcs main.cpp foobar.cpp)
Line 19: Line 20:
  
 
When using KDE4 cmake macros then don't worry about all this. Instead just use the kde4_add_executable macro.
 
When using KDE4 cmake macros then don't worry about all this. Instead just use the kde4_add_executable macro.
 +
 +
==Command Line Usage==
  
 
==Features==
 
==Features==
Line 24: Line 27:
 
==When are which files generated==
 
==When are which files generated==
  
==What doesn't work==
+
==Limitations==

Revision as of 20:36, 16 August 2008

Contents

Usage in CMakeLists.txt

You should not use the automoc4 executable directly. Instead use the FIND_PACKAGE() command to use Automoc4 in your CMakeLists.txt (best use FindAutomoc4.cmake). Then you can add two lines per target to your CMakeLists.txt and you never need to worry about moc files anymore:

set(foobar_srcs main.cpp foobar.cpp)
add_executable(foobar ${foobar_srcs})

then becomes

find_package(Automoc4 REQUIRED)
set(foobar_srcs main.cpp foobar.cpp)
add_automoc4_target(foobar_automoc foobar_srcs)
add_executable(foobar ${foobar_srcs})
add_dependencies(foobar foobar_automoc)

The add_automoc4_target macro adds a new target, which, when called, generates all moc files and a source file to include those when needed and adds the name of that source file to foobar_srcs.

The add_dependencies macro tells cmake to add a dependency such that foobar only gets called after foobar_automoc is done.

When using KDE4 cmake macros then don't worry about all this. Instead just use the kde4_add_executable macro.

Command Line Usage

Features

When are which files generated

Limitations


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal