Stephen Kelly 8266de089c CMake: Create a Qt5::<ModuleName>Private target for each module ... Make it depend on the corresponding Private target of each dependency. This way, user code can write find_package(Qt5Gui REQUIRED) add_executable(hello hello.cpp) target_link_libraries(hello Qt5::GuiPrivate) and get the private include directories for both Qt5Core and Qt5Gui. Don't create the Private target if any of the private include directories do not exist. This way, if user code uses one of the targets, CMake will issue an error if the private include directories do not exist. Unfortunately the error is somewhat cryptic (eg, 'the "Qt5::CorePrivate" was not found'), but this is still an improvement over an error at compile time. This is an improvement on the situation described in QTBUG-37417 using Modern CMake features. Change-Id: I034f8216c3ec64d1a3309682456a713cac9bf854 Reviewed-by: Kai Pastor <dg0yt@darc.de> Reviewed-by: Stephen Kelly <steveire@gmail.com>		2016-12-23 19:24:35 +00:00
..
android	Android Windows: Adjust to new SDK layout	2013-07-04 21:39:24 +02:00
cmake	CMake: Create a Qt5::<ModuleName>Private target for each module	2016-12-23 19:24:35 +00:00
mac	Add tool to namespace Objective-C classes at link time	2016-01-29 14:41:21 +00:00
unix	findclasslist.pl: namespaces can be exported too	2016-10-13 08:29:02 +00:00
configure.json	move definition of configure -continue switch to builtins	2016-12-13 18:55:37 +00:00
dummy.cpp	Implement a more direct headersclean check	2015-04-17 00:54:45 +00:00