cd2690dcbf
If Xcode wasn't configured with any simulators the build would fail since we had no device to build for. But we don't need to build for a specific device, we can build for the generic simulator device, just like we do for the non-simulator build. This likely didn't work properly at the time it was first implemented, but now seems to work fine, and is less fragile than the current solution. Running tests still enumerates the available simulators, as that needs a concrete device to run on. Fixes: COIN-777 Pick-to: 6.2 6.3 5.15 Change-Id: I50e31c1b350cf83ce348275b467051263dea88a9 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> |
||
|---|---|---|
| .. | ||
| aix-g++ | ||
| aix-g++-64 | ||
| android-clang | ||
| common | ||
| cygwin-g++ | ||
| darwin-g++ | ||
| devices | ||
| dummy | ||
| features | ||
| freebsd-clang | ||
| freebsd-g++ | ||
| haiku-g++ | ||
| hpuxi-g++-64 | ||
| hurd-g++ | ||
| integrity-armv7 | ||
| integrity-armv7-imx6 | ||
| integrity-armv8-rcar | ||
| integrity-x86 | ||
| linux-aarch64-gnu-g++ | ||
| linux-arm-gnueabi-g++ | ||
| linux-clang | ||
| linux-clang-32 | ||
| linux-clang-libc++ | ||
| linux-clang-libc++-32 | ||
| linux-g++ | ||
| linux-g++-32 | ||
| linux-g++-64 | ||
| linux-icc | ||
| linux-icc-32 | ||
| linux-icc-64 | ||
| linux-icc-k1om | ||
| linux-llvm | ||
| linux-lsb-g++ | ||
| lynxos-g++ | ||
| macx-clang | ||
| macx-g++ | ||
| macx-icc | ||
| macx-ios-clang | ||
| macx-tvos-clang | ||
| macx-watchos-clang | ||
| macx-xcode | ||
| modules | ||
| netbsd-g++ | ||
| openbsd-g++ | ||
| qnx-aarch64le-qcc | ||
| qnx-armle-v7-qcc | ||
| qnx-x86-64-qcc | ||
| qnx-x86-qcc | ||
| solaris-cc | ||
| solaris-cc-64 | ||
| solaris-cc-64-stlport | ||
| solaris-cc-stlport | ||
| solaris-g++ | ||
| solaris-g++-64 | ||
| unsupported | ||
| wasm-emscripten | ||
| win32-arm64-msvc | ||
| win32-clang-g++ | ||
| win32-clang-msvc | ||
| win32-g++ | ||
| win32-icc | ||
| win32-icc-k1om | ||
| win32-msvc | ||