diff options
| author | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2019-12-05 16:08:11 +0100 |
|---|---|---|
| committer | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2019-12-12 14:56:31 +0100 |
| commit | f733c1c6e70e14fa64923f6601273d3a7d7f2325 (patch) | |
| tree | cc0c0d9582564da806a16b606684ac980f6f3b07 /src/widgets/kernel/qapplication.cpp | |
| parent | 1dca7087e9a8ae6bdeb46be4f57948549c1f7362 (diff) | |
Xcode: Use output directory as SYMROOT when shadow-building
Setting the CONFIGURATION_BUILD_DIR variable to tell Xcode where to
place the final application bundle confuses Xcode when archiving
a project, and the archive ends up without the dSYM files.
Unfortunately we can't leave it up to Xcode to place the build
artifacts wherever it wants, as Qt Creator's iOS support expects
to find the artifacts in a well-defined place. Until we've taught
Qt Creator to find the artifacts for deployment where Xcode placed
them we need to keep this logic.
We now avoid setting the CONFIGURATION_BUILD_DIR variable unless we
really need to due to in-source builds. As long as we're dealing with
a shadow-build it's okey to set SYMROOT.
Change-Id: I9661c1c57725dc8ba5a21f8467b8b61834f2e64d
Fixes: QTBUG-74841
Task-number: QTBUG-52474
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Diffstat (limited to 'src/widgets/kernel/qapplication.cpp')
0 files changed, 0 insertions, 0 deletions