Joerg Bornemann b71c04353d CMake: Work around building dbus 'controller' example with qmake ... Similar to what has been done in 5138a970f3, we need to adjust the remotecontrolledcar/controller dbus example to be built with qmake. In the CI we first build the examples with CMake in the source directory. That creates some generated source files in the dbus example dir. Then, the examples are (will be) built ouf of source with qmake, and those generated source files will be placed in the build directory. When building with MSVC, there's a peculiarity with nmake/jom's inference rules that lead to picking up the generated car_interface.cpp from the source directory, instead of the build directory. See QTBUG-13496 for details. car_interface.cpp, built with CMake is generated to include car_interface.moc. car_interface.cpp, built with qmake does not have this include, but the build system calls moc on car_interface.h. All this leads to duplication of the meta object for OrgExampleExamplesCarInterfaceInterface, preventing successful linking. Work around this issue by turning off the generation of nmake/jom inference rules. Task-number: QTBUG-85986 Change-Id: I0a6ca9f880b63f05a4e9f2032e44d3b391d8a756 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>		2020-11-30 23:17:48 +01:00
..
car	CMake: Regenerate examples to set the WIN32_EXECUTABLE property	2020-10-27 12:49:39 +01:00
controller	CMake: Work around building dbus 'controller' example with qmake	2020-11-30 23:17:48 +01:00
doc	Unify license header usage.	2016-03-29 10:20:03 +00:00
CMakeLists.txt	CMake: Add more examples	2019-03-26 13:03:01 +00:00
remotecontrolledcar.pro	remove QT+=widgets from SUBDIRS projects	2012-12-17 14:08:17 +01:00