Use EXISTS path insead of using find_path because find_path finds the
last target's generated headers, but we want to generate headers for
each target separetely.
Ammends 95c70bbc5bed906fc3d24eebfb00592d48b30a74
Fixes: QTBUG-124800
Change-Id: Ib2b9ceefbc6d11f9bf67fdc6ce25dea3366afe3d
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
(cherry picked from commit 15932205522fc695168f79869fc7d78d65596739)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
By adding Windows App SDK library path, it can be loaded from
that path so in order to run and debug the app via QtCreator, users
won't need to copy Microsoft.WindowsAppRuntime.Bootstrap.dll to the
build path.
Task-number: QTBUG-124800
Change-Id: I33b6ab2bf9ca3ef31ba729b660f134d491aa43ed
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Only x86 and x64 devices have 'x' at the beginning
Task-number: QTBUG-124800
Change-Id: Ia4586fdd8497fa8edb5f26a2e53305fbe2a57d45
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
This CMake file will be included in the user's project.
This script adds a function called "qt_add_win_app_sdk".
This function needs to be called in the user's project's CMake file.
This is the first step to bring Windows App SDK functionality to Qt
apps and it might be enough. For now there is not enough reason to
integrate Windows App SDK into Qt. Title bar customization can be done
without needing the SDK, and WebView2 can also be used independently.
Task-number: QTBUG-124800
Change-Id: Icd4ca2c51783942cbb8bfe1c274162628b92a115
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
