|
@@ -111,12 +111,14 @@
|
|
|
#
|
|
#
|
|
|
# ::
|
|
# ::
|
|
|
#
|
|
#
|
|
|
-# macro QT4_ADD_DBUS_ADAPTOR(outfiles xmlfile parentheader parentclassname [basename] [classname])
|
|
|
|
|
|
|
+# macro QT4_ADD_DBUS_ADAPTOR(outfiles xmlfile parentheader parentclassname
|
|
|
|
|
+# [basename] [classname])
|
|
|
# create a dbus adaptor (header and implementation file) from the xml file
|
|
# create a dbus adaptor (header and implementation file) from the xml file
|
|
|
# describing the interface, and add it to the list of sources. The adaptor
|
|
# describing the interface, and add it to the list of sources. The adaptor
|
|
|
# forwards the calls to a parent class, defined in parentheader and named
|
|
# forwards the calls to a parent class, defined in parentheader and named
|
|
|
# parentclassname. The name of the generated files will be
|
|
# parentclassname. The name of the generated files will be
|
|
|
-# <basename>adaptor.{cpp,h} where basename defaults to the basename of the xml file.
|
|
|
|
|
|
|
+# <basename>adaptor.{cpp,h} where basename defaults to the basename of the
|
|
|
|
|
+# xml file.
|
|
|
# If <classname> is provided, then it will be used as the classname of the
|
|
# If <classname> is provided, then it will be used as the classname of the
|
|
|
# adaptor itself.
|
|
# adaptor itself.
|
|
|
#
|
|
#
|
|
@@ -128,7 +130,8 @@
|
|
|
# If the optional argument interfacename is omitted, the name of the
|
|
# If the optional argument interfacename is omitted, the name of the
|
|
|
# interface file is constructed from the basename of the header with
|
|
# interface file is constructed from the basename of the header with
|
|
|
# the suffix .xml appended.
|
|
# the suffix .xml appended.
|
|
|
-# Options may be given to qdbuscpp2xml, such as those found when executing "qdbuscpp2xml --help"
|
|
|
|
|
|
|
+# Options may be given to qdbuscpp2xml, such as those found when
|
|
|
|
|
+# executing "qdbuscpp2xml --help"
|
|
|
#
|
|
#
|
|
|
#
|
|
#
|
|
|
# ::
|
|
# ::
|
|
@@ -170,10 +173,11 @@
|
|
|
# want to use QT4_WRAP_CPP() (which is reliable and mature), you can insert
|
|
# want to use QT4_WRAP_CPP() (which is reliable and mature), you can insert
|
|
|
# #include "foo.moc"
|
|
# #include "foo.moc"
|
|
|
# in foo.cpp and then give foo.cpp as argument to QT4_AUTOMOC(). This will the
|
|
# in foo.cpp and then give foo.cpp as argument to QT4_AUTOMOC(). This will the
|
|
|
-# scan all listed files at cmake-time for such included moc files and if it finds
|
|
|
|
|
-# them cause a rule to be generated to run moc at build time on the
|
|
|
|
|
|
|
+# scan all listed files at cmake-time for such included moc files and if it
|
|
|
|
|
+# finds them cause a rule to be generated to run moc at build time on the
|
|
|
# accompanying header file foo.h.
|
|
# accompanying header file foo.h.
|
|
|
-# If a source file has the SKIP_AUTOMOC property set it will be ignored by this macro.
|
|
|
|
|
|
|
+# If a source file has the SKIP_AUTOMOC property set it will be ignored by
|
|
|
|
|
+# this macro.
|
|
|
# If the <tgt> is specified, the INTERFACE_INCLUDE_DIRECTORIES and
|
|
# If the <tgt> is specified, the INTERFACE_INCLUDE_DIRECTORIES and
|
|
|
# INTERFACE_COMPILE_DEFINITIONS from the <tgt> are passed to moc.
|
|
# INTERFACE_COMPILE_DEFINITIONS from the <tgt> are passed to moc.
|
|
|
#
|
|
#
|
|
@@ -181,16 +185,17 @@
|
|
|
# ::
|
|
# ::
|
|
|
#
|
|
#
|
|
|
# function QT4_USE_MODULES( target [link_type] modules...)
|
|
# function QT4_USE_MODULES( target [link_type] modules...)
|
|
|
-# This function is obsolete. Use target_link_libraries with IMPORTED targets instead.
|
|
|
|
|
|
|
+# This function is obsolete. Use target_link_libraries with IMPORTED targets
|
|
|
|
|
+# instead.
|
|
|
# Make <target> use the <modules> from Qt. Using a Qt module means
|
|
# Make <target> use the <modules> from Qt. Using a Qt module means
|
|
|
# to link to the library, add the relevant include directories for the module,
|
|
# to link to the library, add the relevant include directories for the module,
|
|
|
# and add the relevant compiler defines for using the module.
|
|
# and add the relevant compiler defines for using the module.
|
|
|
# Modules are roughly equivalent to components of Qt4, so usage would be
|
|
# Modules are roughly equivalent to components of Qt4, so usage would be
|
|
|
# something like:
|
|
# something like:
|
|
|
# qt4_use_modules(myexe Core Gui Declarative)
|
|
# qt4_use_modules(myexe Core Gui Declarative)
|
|
|
-# to use QtCore, QtGui and QtDeclarative. The optional <link_type> argument can
|
|
|
|
|
-# be specified as either LINK_PUBLIC or LINK_PRIVATE to specify the same argument
|
|
|
|
|
-# to the target_link_libraries call.
|
|
|
|
|
|
|
+# to use QtCore, QtGui and QtDeclarative. The optional <link_type> argument
|
|
|
|
|
+# can be specified as either LINK_PUBLIC or LINK_PRIVATE to specify the
|
|
|
|
|
+# same argument to the target_link_libraries call.
|
|
|
#
|
|
#
|
|
|
#
|
|
#
|
|
|
# IMPORTED Targets
|
|
# IMPORTED Targets
|