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
..
ExtraSourceIncludes.cmake.in	Generate source includes in a separate file, if needed.	2013-10-16 15:30:13 +02:00
Qt5BasicConfig.cmake.in	CMake: Create a Qt5::<ModuleName>Private target for each module	2016-12-23 19:24:35 +00:00
Qt5ConfigVersion.cmake.in	Remove CMake warning	2015-12-28 22:37:22 +00:00
Qt5PluginTarget.cmake.in	Teach CMake about Qt 5 plugins.	2013-09-10 14:38:18 +02:00