Forums

OverviewFelgo 2 Support (Qt 5) › Compiling example project "AppPlayground" for Android and IOS

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #22351

    Juan Sebastian Pena Rodriguez

    Hello,

    I’m new to the system and the first thing I try to do is to compile one of the example projects and try to run it in a simulator, sadly I’m not able to do it, any Ideas why?

     

    — IOS console output —

    19:52:51: Running steps for project AppPlayground…

    19:52:51: Starting: “/Users/juan/Felgo/Felgo/ios/bin/qmake” /Users/juan/Felgo/Examples/Felgo/playground/AppPlayground/AppPlayground.pro -spec macx-ios-clang CONFIG+=iphonesimulator CONFIG+=simulator CONFIG+=qml_debug

    19:52:54: The process “/Users/juan/Felgo/Felgo/ios/bin/qmake” exited normally.

    19:52:54: Starting: “/usr/bin/make” -f /Users/juan/Felgo/Examples/Felgo/playground/build-AppPlayground-Qt_5_12_3_iOS_Felgo_Simulator-Debug/Makefile qmake_all

    Traceback (most recent call last):

    File “/Users/juan/Felgo/Felgo/ios/mkspecs/features/uikit/devices.py”, line 78, in <module>

    if is_suitable_runtime(runtimes, runtime_name, args.platform, args.minimum_deployment_target):

    File “/Users/juan/Felgo/Felgo/ios/mkspecs/features/uikit/devices.py”, line 53, in is_suitable_runtime

    and “unavailable” not in runtime[“availability”] \

    KeyError: ‘availability’

    make: Nothing to be done for `qmake_all’.

    19:52:54: The process “/usr/bin/make” exited normally.

    19:52:54: Starting: “/usr/bin/make” -j12

    Traceback (most recent call last):

    File “/Users/juan/Felgo/Felgo/ios/mkspecs/features/uikit/devices.py”, line 78, in <module>

    if is_suitable_runtime(runtimes, runtime_name, args.platform, args.minimum_deployment_target):

    File “/Users/juan/Felgo/Felgo/ios/mkspecs/features/uikit/devices.py”, line 53, in is_suitable_runtime

    and “unavailable” not in runtime[“availability”] \

    KeyError: ‘availability’

    xcodebuild build -project AppPlayground.xcodeproj -scheme AppPlayground -configuration Debug -destination “id=” -destination-timeout 1 ENABLE_ONLY_ACTIVE_RESOURCES=NO

    xcodebuild: error: missing value for key ‘id’ of option ‘Destination’

    Usage: xcodebuild [-project <projectname>] [[-target <targetname>]…|-alltargets] [-configuration <configurationname>] [-arch <architecture>]… [-sdk [<sdkname>|<sdkpath>]] [-showBuildSettings [-json]] [<buildsetting>=<value>]… [<buildaction>]…

    xcodebuild [-project <projectname>] -scheme <schemeName> [-destination <destinationspecifier>]… [-configuration <configurationname>] [-arch <architecture>]… [-sdk [<sdkname>|<sdkpath>]] [-showBuildSettings [-json]] [-showdestinations] [<buildsetting>=<value>]… [<buildaction>]…

    xcodebuild -workspace <workspacename> -scheme <schemeName> [-destination <destinationspecifier>]… [-configuration <configurationname>] [-arch <architecture>]… [-sdk [<sdkname>|<sdkpath>]] [-showBuildSettings] [-showdestinations] [<buildsetting>=<value>]… [<buildaction>]…

    xcodebuild -version [-sdk [<sdkfullpath>|<sdkname>] [-json] [<infoitem>] ]

    xcodebuild -list [[-project <projectname>]|[-workspace <workspacename>]] [-json]

    xcodebuild -showsdks [-json]

    xcodebuild -exportArchive -archivePath <xcarchivepath> [-exportPath <destinationpath>] -exportOptionsPlist <plistpath>

    xcodebuild -exportNotarizedApp -archivePath <xcarchivepath> -exportPath <destinationpath>

    xcodebuild -exportLocalizations -localizationPath <path> -project <projectname> [-exportLanguage <targetlanguage>…[-includeScreenshots]]

    xcodebuild -importLocalizations -localizationPath <path> -project <projectname>

    xcodebuild -resolvePackageDependencies [-project <projectname>|-workspace <workspacename>] -clonedSourcePackagesDirPath <path>

    xcodebuild -create-xcframework [-help] [-framework <path>] [-library <path> [-headers <path>]] -output <path>

    Options:

    -usage print brief usage

    -help print complete usage

    -verbose provide additional status output

    -license show the Xcode and SDK license agreements

    -checkFirstLaunchStatus Check if any First Launch tasks need to be performed

    -runFirstLaunch install packages and agree to the license

    -project NAME build the project NAME

    -target NAME build the target NAME

    -alltargets build all targets

    -workspace NAME build the workspace NAME

    -scheme NAME build the scheme NAME

    -configuration NAME use the build configuration NAME for building each target

    -xcconfig PATH apply the build settings defined in the file at PATH as overrides

    -arch ARCH build each target for the architecture ARCH; this will override architectures defined in the project

    -sdk SDK use SDK as the name or path of the base SDK when building the project

    -toolchain NAME use the toolchain with identifier or name NAME

    -destination DESTINATIONSPECIFIER use the destination described by DESTINATIONSPECIFIER (a comma-separated set of key=value pairs describing the destination to use)

    -destination-timeout TIMEOUT wait for TIMEOUT seconds while searching for the destination device

    -parallelizeTargets build independent targets in parallel

    -jobs NUMBER specify the maximum number of concurrent build operations

    -maximum-concurrent-test-device-destinations NUMBER the maximum number of device destinations to test on concurrently

    -maximum-concurrent-test-simulator-destinations NUMBER the maximum number of simulator destinations to test on concurrently

    -parallel-testing-enabled YES|NO overrides the per-target setting in the scheme

    -parallel-testing-worker-count NUMBER the exact number of test runners that will be spawned during parallel testing

    -maximum-parallel-testing-workers NUMBER the maximum number of test runners that will be spawned during parallel testing

    -dry-run do everything except actually running the commands

    -quiet do not print any output except for warnings and errors

    -hideShellScriptEnvironment don’t show shell script environment variables in build log

    -showsdks display a compact list of the installed SDKs

    -showdestinations display a list of destinations

    -showTestPlans display a list of test plans

    -showBuildSettings display a list of build settings and values

    -list lists the targets and configurations in a project, or the schemes in a workspace

    -find-executable NAME display the full path to executable NAME in the provided SDK and toolchain

    -find-library NAME display the full path to library NAME in the provided SDK and toolchain

    -version display the version of Xcode; with -sdk will display info about one or all installed SDKs

    -enableAddressSanitizer YES|NO turn the address sanitizer on or off

    -enableThreadSanitizer YES|NO turn the thread sanitizer on or off

    -enableUndefinedBehaviorSanitizer YES|NO turn the undefined behavior sanitizer on or off

    -resultBundlePath PATH specifies the directory where a result bundle describing what occurred will be placed

    -resultStreamPath PATH specifies the file where a result stream will be written to (the file must already exist)

    -resultBundleVersion 3 [default] specifies which result bundle version should be used

    -clonedSourcePackagesDirPath PATH specifies the directory to which remote source packages are fetch or expected to be found

    -derivedDataPath PATH specifies the directory where build products and other derived data will go

    -archivePath PATH specifies the directory where any created archives will be placed, or the archive that should be exported

    -exportArchive specifies that an archive should be exported

    -exportNotarizedApp export an archive that has been notarized by Apple

    -exportOptionsPlist PATH specifies a path to a plist file that configures archive exporting

    -enableCodeCoverage YES|NO turn code coverage on or off when testing

    -exportPath PATH specifies the destination for the product exported from an archive

    -skipUnavailableActions specifies that scheme actions that cannot be performed should be skipped instead of causing a failure

    -exportLocalizations exports completed and outstanding project localizations

    -importLocalizations imports localizations for a project, assuming any necessary localized resources have been created in Xcode

    -localizationPath specifies a path to XLIFF localization files

    -exportLanguage specifies multiple optional ISO 639-1 languages included in a localization export

    -xctestrun specifies a path to a test run specification

    -testPlan specifies the name of the test plan associated with the scheme to use for testing

    -only-testing constrains testing by specifying tests to include, and excluding other tests

    -only-testing:TEST-IDENTIFIER constrains testing by specifying tests to include, and excluding other tests

    -skip-testing constrains testing by specifying tests to exclude, but including other tests

    -skip-testing:TEST-IDENTIFIER constrains testing by specifying tests to exclude, but including other tests

    -only-test-configuration constrains testing by specifying test configurations to include, and excluding other test configurations

    -skip-test-configuration constrains testing by specifying test configurations to exclude, but including other test configurations

    -testLanguage constrains testing by specifying ISO 639-1 language in which to run the tests

    -testRegion constrains testing by specifying ISO 3166-1 region in which to run the tests

    -resolvePackageDependencies resolves any Swift package dependencies referenced by the project or workspace

    -disableAutomaticPackageResolution prevents packages from automatically being resolved to versions other than those recorded in the Package.resolved file

    -json output as JSON (note: -json implies -quiet)

    -allowProvisioningUpdates Allow xcodebuild to communicate with the Apple Developer website. For automatically signed targets, xcodebuild will create and update profiles, app IDs, and certificates. For manually signed targets, xcodebuild will download missing or updated provisioning profiles. Requires a developer account to have been added in Xcode’s Accounts preference pane.

    -allowProvisioningDeviceRegistration Allow xcodebuild to register your destination device on the developer portal if necessary. This flag only takes effect if -allowProvisioningUpdates is also passed.

    -showBuildTimingSummary display a report of the timings of all the commands invoked during the build

    -create-xcframework create an xcframework from prebuilt libraries; -help for more information.

    make: *** [xcodebuild-debug-simulator] Error 64

    19:52:55: The process “/usr/bin/make” exited with code 2.

    Error while building/deploying project AppPlayground (kit: Qt 5.12.3 iOS Felgo Simulator)

    When executing step “Make”

    19:52:55: Elapsed time: 00:03.

     

    — Android Output —

    20:04:45: Running steps for project AppPlayground…

    20:04:45: Configuration unchanged, skipping qmake step.

    20:04:45: Starting: “/Users/juan/Library/Android/sdk/ndk/20.1.5948944/prebuilt/darwin-x86_64/bin/make” -j12

    /Users/juan/Library/Android/sdk/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ -D__ANDROID_API__=28 -target i686-none-linux-android -mstackrealign -gcc-toolchain /Users/juan/Library/Android/sdk/ndk/20.1.5948944/toolchains/x86-4.9/prebuilt/darwin-x86_64 -fno-limit-debug-info -Wl,–exclude-libs,libgcc.a -Wl,–exclude-libs,libatomic.a –sysroot=/Users/juan/Library/Android/sdk/ndk/20.1.5948944/platforms/android-28/arch-x86/ -Wl,-soname,libAppPlayground.so -Wl,-rpath=/Users/juan/Felgo/Felgo/android_x86/lib -Wl,–no-undefined -Wl,-z,noexecstack -shared -o libAppPlayground.so main.o qrc_resources_user.o -L/Users/juan/Felgo/Felgo/android_x86/lib -lFelgo -lcrypto -lssl -lQt5Quick -L/opt/android/android-ndk-r18b/sources/cxx-stl/llvm-libc++/libs/x86 -lQt5Widgets -lQt5Multimedia -lQt5Gui -lQt5Qml -lQt5WebSockets -lQt5Network -lQt5Sql -lQt5Core -lGLESv2 -L/Users/juan/Library/Android/sdk/ndk/20.1.5948944/sources/cxx-stl/llvm-libc++/libs/x86 /Users/juan/Library/Android/sdk/ndk/20.1.5948944/sources/cxx-stl/llvm-libc++/libs/x86/libc++.so.28 -llog -lz -lm -ldl -lc

    /Users/juan/Library/Android/sdk/ndk/20.1.5948944/toolchains/x86-4.9/prebuilt/darwin-x86_64/lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot find -lc++

    clang++: error: linker command failed with exit code 1 (use -v to see invocation)

    make: *** [libAppPlayground.so] Error 1

    20:04:45: The process “/Users/juan/Library/Android/sdk/ndk/20.1.5948944/prebuilt/darwin-x86_64/bin/make” exited with code 2.

    Error while building/deploying project AppPlayground (kit: Android for x86 (Clang Qt 5.12.3 Android x86 Felgo))

    When executing step “Make”

    20:04:46: Elapsed time: 00:01.

     

    PS: I try to compile one of the examples in Qt 5.13.2 “Bluetooth Low Energy Heart Rate Game” and everything works fine

    #22409

    Alex
    Felgo Team

    Hi Juan,

    this is very strange, I must have forgot to hit send on my reply, or Google captcha got me bad, I swear I already wrote an answer here last week. I hope you enjoyed Qt World Summit, it was nice meeting you!

    Please use the recommended NDK version from the Android deployment docs, which is currently 19c. This is most probably the root of this issue.

    Cheers,
    Alex

    #22411

    Juan Sebastian Pena Rodriguez

    Hi Alex,

    Thanks for the answer, no worries it can happen times to times 😊. Ok that may explain Android, but how about IOS?

    Yes It was nice meeting you too

     

    Best regards,

    Juan.

    #22412

    Alex
    Felgo Team

    My bad, I missed the iOS part.

    The KeyError “availability” matches user reports of XCode not picking up the correct profile when auto-signing the app. Could you check if manually selecting the correct settings and deploying from Xcode works?

    Also this thread or other Qt related answers for “[xcodebuild-debug-simulator] Error 64” might help there: https://forum.qt.io/topic/105200/error-building-the-application-ios-using-qtcreator

    Cheers,
    Alex

Viewing 4 posts - 1 through 4 (of 4 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Voted #1 for:

  • Easiest to learn
  • Most time saving
  • Best support

Develop Cross-Platform Apps and Games 50% Faster!

  • Voted the best supported, most time-saving and easiest to learn cross-platform development tool
  • Based on the Qt framework, with native performance and appearance on all platforms including iOS and Android
  • Offers a variety of plugins to monetize, analyze and engage users
FREE!
create apps
create games
cross platform
native performance
3rd party services
game network
multiplayer
level editor
easiest to learn
biggest time saving
best support