Re: [Qbs] Set cpp properties for generated cpp files (moc) does not seem to work
On Thu, 14 May 2020 14:49:25 + Maximilian Hrabowski wrote: > Isn’t unmocable used to tag cpp/header files that should not be processed by > moc? Sure, that's why the generated cpp files get it, so they won't get processed again. Christian ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Set cpp properties for generated cpp files (moc) does not seem to work
On Thu, 14 May 2020 12:22:53 +
Maximilian Hrabowski wrote:
> we have quite a strict warning policy so all warnings are treated as errors
> in our code. This creates problems when including third-party code that
> produces warnings, so usually those files are put in a special group and
> warningsAreErrors is turned off:
>
> Group {
> …
> cpp.treatWarningsAsErrors: false
> }
>
> This usually works quite well. But now i’ve got the problem that i need to
> disable this for cpp files generated by moc. I tried the following approach
> but it does not seem to work:
>
> Group {
> fileTagsFilter: [“moc_cpp"]
"moc_cpp" is for files to be included. As those won't get compiled, this
property has no effect.
You might be able to approximate what you want by using "unmocable" here.
> cpp.treatWarningsAsErrors: false
> }
Christian
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
On Fri, 15 May 2020 at 01:01, Raphael Cotty wrote: > > Hi, > Yes, I use qtc to load my multi-arch app. Maybe it's my Android env then. I'm using SDK 26.1, Ndk 21.2 and Platform 28 Build tools are pinned to 28.0.3, not sure if it's a strict requirement for me. Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
Hi, Yes, I use qtc to load my multi-arch app. Raph Le jeu. 14 mai 2020 à 14:37, Christian Gagneraud a écrit : > On Fri, 15 May 2020 at 00:28, Christian Gagneraud > wrote: > > > > On Fri, 15 May 2020 at 00:23, Raphael Cotty > wrote: > > > > > > Hi, > > > Can you try to use the QtApplication item instead of the > CppApplication one? > > > > Hey, spot on! This solves the problem. > > Thanks a lot for that! > Can you create and load multi-arch binaries with QtC + Qbs? > > Chris > ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Qtc: Cannot find the androiddeploy Json file
On Fri, 15 May 2020 at 00:45, Christian Gagneraud wrote: > > On Fri, 15 May 2020 at 00:16, Raphael Cotty wrote: > > > > Hi, > > The json file used in android_support.qbs is an input file used by the > > androiddeployqt tool to generate the apk. > > Here, the term deploy refers to gathering all the qt dependencies (qt libs, > > plugins...) in a directory in order to generate the apk. > > > > The json file you talk about looks more to me to something linked to the > > deployment on the target. > > Any idea of the json file name when it works? > When run by qbs: > /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/androiddeployqt.json > > But this time, QtC didn't try to run androiddeployqt, honestly the > behaviour seems to be unstable. > > adb install fails. It's possible that these sort of APK are not > supported by our AOSP. > I'll ask someone if this is supposed to work or not. From QtC: Initializing deployment to Android device/simulator Deploying to 150c980e8288de07 00:50:34: Running steps for project Neon Factory Tools... 00:50:34: Starting: "/home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07 install -r /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/factory-testapp-0.0.apk" 00:50:34: The process "/home/chgans/Android/Sdk/platform-tools/adb" exited with code 255. When i copy/paste the command in a terminal, it doesn't fail: chgans@chgans-pc:~/Projects/neon-testapp$ /home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07 install -r /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/factory-testapp-0.0.apk Performing Streamed Install Success chgans@chgans-pc:~/Projects/neon-testapp$ echo $? 0 Will report on QtC ML. Thanks again for your help! Chris > > Thanks, > Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Qtc: Cannot find the androiddeploy Json file
On Fri, 15 May 2020 at 00:16, Raphael Cotty wrote: > > Hi, > The json file used in android_support.qbs is an input file used by the > androiddeployqt tool to generate the apk. > Here, the term deploy refers to gathering all the qt dependencies (qt libs, > plugins...) in a directory in order to generate the apk. > > The json file you talk about looks more to me to something linked to the > deployment on the target. > Any idea of the json file name when it works? When run by qbs: /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/androiddeployqt.json But this time, QtC didn't try to run androiddeployqt, honestly the behaviour seems to be unstable. adb install fails. It's possible that these sort of APK are not supported by our AOSP. I'll ask someone if this is supposed to work or not. Thanks, Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
On Fri, 15 May 2020 at 00:28, Christian Gagneraud wrote: > > On Fri, 15 May 2020 at 00:23, Raphael Cotty wrote: > > > > Hi, > > Can you try to use the QtApplication item instead of the CppApplication one? > > Hey, spot on! This solves the problem. Thanks a lot for that! Can you create and load multi-arch binaries with QtC + Qbs? Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
On Fri, 15 May 2020 at 00:23, Raphael Cotty wrote: > > Hi, > Can you try to use the QtApplication item instead of the CppApplication one? Hey, spot on! This solves the problem. Now i have other problems, but this time it's QtC, QtC wants to run androiddeployqt again with --no-build --gradle --reinstall --device And it's adb pulling app_process, linker, libc.so, ... Weird stuff! Maybe i need to tweak a few things in QtC. Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
On Fri, 15 May 2020 at 00:20, Raphael Cotty wrote:
>
> Hi,
> Can you enable androiddeployqt debug:
> Qt.android_support.verboseAndroidDeployQt
> And provide the output file?
00:21:53: Running steps for project Neon Factory Tools...
copying Qt resource templates [TestApp]
running androiddeployqt [TestApp]
/home/chgans/Programs/QtCommercial/5.14.2/android/bin/androiddeployqt
--output
/home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/deployqt_out
--input
/home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/androiddeployqt.json
--aux-mode --deployment bundled --android-platform android-28
--verbose
Cannot find application binary TestApp.
Process failed with exit code 2.
The following products could not be built for configuration
Debug_Android__54f9cea5714846ce:
TestApp
Error while building/deploying project Neon Factory Tools (kit:
Android for armeabi-v7a,arm64-v8a,x86,x86_64 (Clang Qt 5.14.2 for
Android))
When executing step "Qbs Build"
00:21:53: Elapsed time: 00:00.
And json:
{
"description": "This file was generated by qbs to be read by
androiddeployqt and should not be modified by hand.",
"qt": "/home/chgans/Programs/QtCommercial/5.14.2/android",
"sdk": "/home/chgans/Android/Sdk",
"sdkBuildToolsRevision": "28.0.3",
"ndk": "/home/chgans/Android/Sdk/ndk-bundle",
"toolchain-prefix": "llvm",
"tool-prefix": "llvm",
"useLLVM": true,
"ndk-host": "linux-x86_64",
"architectures":
{"x86_64":"x86_64-linux-android","arm64-v8a":"aarch64-linux-android"},
"qml-root-path": "/home/chgans/Projects/neon-testapp/sources/TestApp",
"stdcpp-path":
"/home/chgans/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/",
"application-binary": "TestApp"
}
Thanks,
Chris
> Thanks
> Raph
>
> Le jeu. 14 mai 2020 à 14:12, Christian Gagneraud a écrit :
>>
>> On Thu, 14 May 2020 at 23:34, Christian Gagneraud wrote:
>> >
>> > Hi there,
>> >
>> > As an experiment, i've just tried Qt-5.14, and this has enabled
>> > multi-arch on Android.
>> > I can select the list of architecture i want to support with
>> > qbs.architectures.
>> > This works for libraries, but my application is disabled:
>> > Error while handling 'TestApp'
>> > Product 'TestApp' had errors and was disabled.
>>
>> I've tracked the problem down into one library, I have an export item
>> that seems to be problematic.
>> For now i added an explicit dependency in the app, and removed the export.
>> Looks weird...
>>
>> But now androiddeployqt fails with:
>> Cannot find application binary TestApp
>> Don't know why it's not one of the libTestApp.so, ...
>>
>> Chris
>> ___
>> Qbs mailing list
>> Qbs@qt-project.org
>> https://lists.qt-project.org/listinfo/qbs
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
Hi,
Can you try to use the QtApplication item instead of the CppApplication one?
Raph
Le jeu. 14 mai 2020 à 14:20, Christian Gagneraud a
écrit :
> On Thu, 14 May 2020 at 23:57, Richard Weickelt
> wrote:
> >
> >
> > > As an experiment, i've just tried Qt-5.14, and this has enabled
> > > multi-arch on Android.
> > > I can select the list of architecture i want to support with
> qbs.architectures.
> > > This works for libraries, but my application is disabled:
> > > Error while handling 'TestApp'
> > > Product 'TestApp' had errors and was disabled.
> > >
> > > 3 of them, and that's all i get. I have 3 Depends that point to
> > > internal libraries, maybe that's the smoking gun...
> > > I have
> > > multiplexByQbsProperties: ["architectures"]
> > > qbs.architectures: ["arm64", "x86_64"]
> > > For libs and apps.
> > > I tried as well the 'usesNativeCode' but no success.
> > >
> > > Any idea what i'm missing?
> >
> > Can you show us some more code or even a minimal example?
>
> Here is my app module:
> CppApplication {
> Depends { name: "Qt.core" }
> Depends { name: "Qt.androidextras"; condition: qbs.targetPlatform
> == "android" }
> cpp.includePaths: [ project.sourceDirectory + "/sources", "." ]
> cpp.cxxLanguageVersion: "c++14"
> qbs.architectures: ["arm64", "x86_64"]
> multiplexByQbsProperties: ["architectures", "profiles"]
>
> Properties {
> condition: qbs.targetPlatform == "android"
> // https://x
> Android.sdk.platform: "android-28"
> Android.sdk.buildToolsVersion: "28.0.3"
> Android.ndk.platform: "android-28"
> // Apk
> Android.sdk.packageName: "." + name.toLowerCase()
> Android.sdk.versionName: project.versionName
> Android.sdk.versionCode: project.versionCode
> Android.sdk.apkBaseName: "factory-" + name.toLowerCase() + "-"
> + project.versionName
> Android.sdk.manifestFile: sourceDirectory +
> "/android/AndroidManifest.xml"
> Android.sdk.keyStorePath: project.sourceDirectory + "/.jks"
> Android.sdk.keyStorePassword: ":x"
> Android.sdk.keyAlias: "xx"
> Android.sdk.keyPassword: ":x"
> // For debugging androiddeployqt issues, set this to true
> // androiddeployqt is only use by qbs to collect dependencies
> //Qt.android_support.verboseAndroidDeployQt: true
> }
> }
>
> And my library module:
> StaticLibrary {
>
> Depends { name: "Qt.core" }
> Depends { name: "Qt.androidextras"; condition: qbs.targetPlatform
> == "android" }
>
> cpp.includePaths: [ project.sourceDirectory + "/sources", "." ]
> cpp.cxxLanguageVersion: "c++14"
> multiplexByQbsProperties: ["architectures", "profiles"]
> qbs.architectures: ["arm64", "x86_64"]
> }
>
> First time i'm using multi-arch, my understanding is that i should
> have 1 APK that support these 2 archs
>
> Chris
> ___
> Qbs mailing list
> Qbs@qt-project.org
> https://lists.qt-project.org/listinfo/qbs
>
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
[Qbs] Set cpp properties for generated cpp files (moc) does not seem to work
Hi all,
we have quite a strict warning policy so all warnings are treated as errors in
our code. This creates problems when including third-party code that produces
warnings, so usually those files are put in a special group and
warningsAreErrors is turned off:
Group {
…
cpp.treatWarningsAsErrors: false
}
This usually works quite well. But now i’ve got the problem that i need to
disable this for cpp files generated by moc. I tried the following approach but
it does not seem to work:
Group {
fileTagsFilter: [“moc_cpp"]
cpp.treatWarningsAsErrors: false
}
is this supposed to work and probably a bug (maybe related to
https://bugreports.qt.io/browse/QBS-1030) or are my expectations wrong…
Cheers,
Maximilian
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
Hi, Can you enable androiddeployqt debug: Qt.android_support.verboseAndroidDeployQt And provide the output file? Thanks Raph Le jeu. 14 mai 2020 à 14:12, Christian Gagneraud a écrit : > On Thu, 14 May 2020 at 23:34, Christian Gagneraud > wrote: > > > > Hi there, > > > > As an experiment, i've just tried Qt-5.14, and this has enabled > > multi-arch on Android. > > I can select the list of architecture i want to support with > qbs.architectures. > > This works for libraries, but my application is disabled: > > Error while handling 'TestApp' > > Product 'TestApp' had errors and was disabled. > > I've tracked the problem down into one library, I have an export item > that seems to be problematic. > For now i added an explicit dependency in the app, and removed the export. > Looks weird... > > But now androiddeployqt fails with: > Cannot find application binary TestApp > Don't know why it's not one of the libTestApp.so, ... > > Chris > ___ > Qbs mailing list > Qbs@qt-project.org > https://lists.qt-project.org/listinfo/qbs > ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
On Thu, 14 May 2020 at 23:57, Richard Weickelt wrote:
>
>
> > As an experiment, i've just tried Qt-5.14, and this has enabled
> > multi-arch on Android.
> > I can select the list of architecture i want to support with
> > qbs.architectures.
> > This works for libraries, but my application is disabled:
> > Error while handling 'TestApp'
> > Product 'TestApp' had errors and was disabled.
> >
> > 3 of them, and that's all i get. I have 3 Depends that point to
> > internal libraries, maybe that's the smoking gun...
> > I have
> > multiplexByQbsProperties: ["architectures"]
> > qbs.architectures: ["arm64", "x86_64"]
> > For libs and apps.
> > I tried as well the 'usesNativeCode' but no success.
> >
> > Any idea what i'm missing?
>
> Can you show us some more code or even a minimal example?
Here is my app module:
CppApplication {
Depends { name: "Qt.core" }
Depends { name: "Qt.androidextras"; condition: qbs.targetPlatform
== "android" }
cpp.includePaths: [ project.sourceDirectory + "/sources", "." ]
cpp.cxxLanguageVersion: "c++14"
qbs.architectures: ["arm64", "x86_64"]
multiplexByQbsProperties: ["architectures", "profiles"]
Properties {
condition: qbs.targetPlatform == "android"
// https://x
Android.sdk.platform: "android-28"
Android.sdk.buildToolsVersion: "28.0.3"
Android.ndk.platform: "android-28"
// Apk
Android.sdk.packageName: "." + name.toLowerCase()
Android.sdk.versionName: project.versionName
Android.sdk.versionCode: project.versionCode
Android.sdk.apkBaseName: "factory-" + name.toLowerCase() + "-"
+ project.versionName
Android.sdk.manifestFile: sourceDirectory +
"/android/AndroidManifest.xml"
Android.sdk.keyStorePath: project.sourceDirectory + "/.jks"
Android.sdk.keyStorePassword: ":x"
Android.sdk.keyAlias: "xx"
Android.sdk.keyPassword: ":x"
// For debugging androiddeployqt issues, set this to true
// androiddeployqt is only use by qbs to collect dependencies
//Qt.android_support.verboseAndroidDeployQt: true
}
}
And my library module:
StaticLibrary {
Depends { name: "Qt.core" }
Depends { name: "Qt.androidextras"; condition: qbs.targetPlatform
== "android" }
cpp.includePaths: [ project.sourceDirectory + "/sources", "." ]
cpp.cxxLanguageVersion: "c++14"
multiplexByQbsProperties: ["architectures", "profiles"]
qbs.architectures: ["arm64", "x86_64"]
}
First time i'm using multi-arch, my understanding is that i should
have 1 APK that support these 2 archs
Chris
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Qtc: Cannot find the androiddeploy Json file
Hi,
The json file used in android_support.qbs is an input file used by the
androiddeployqt tool to generate the apk.
Here, the term deploy refers to gathering all the qt dependencies (qt libs,
plugins...) in a directory in order to generate the apk.
The json file you talk about looks more to me to something linked to the
deployment on the target.
Any idea of the json file name when it works?
Raph
Le jeu. 14 mai 2020 à 11:52, Christian Gagneraud a
écrit :
> On Tue, 12 May 2020 at 18:37, Richard Weickelt
> wrote:
> >
> >
> > > When i want to "run" on the device:
> > > Initializing deployment to Android device/simulator
> > > Deploying to 150c980e8288de07
> > > Cannot find the androiddeploy Json file.
> > > Error while building/deploying project Neon Factory Tools (kit:
> > > Android for arm64-v8a (Clang Qt 5.12.8 for Android ARM64-v8a))
> > > When executing step "Deploy to Android device"
> > >
> > > I think this happens only when i do cosmetic changes in my qbs files.
> > > The only way to recover is to trigger a manual build, changing a
> > > source file is not enough.
> > >
> > > Any idea what's goind on?
> > > Looks to me this problem is on QtC side.
> >
> > A quick guess and without ever having built an Android project: The
> selected
> > product is the application executable and thus, none of the subsequent
> rules
> > is executed. Could that explain it? Have a look at
> >
> https://code.qt.io/cgit/qbs/qbs.git/tree/share/qbs/module-providers/Qt/templates/android_support.qbs
> > There is a rule that produces qt_androiddeployqt_input (the json file)
> which
> > I guess is not requested when you press the "run" button. There are also
> > subsequent rules responsible for the deployment.
> >
> > You could add one of the rule's output to your product type, although I
> > guess there is a cleaner way of doing it.
> >
> > YourAndroidProduct {
> > type: base.concat("bundled_jar")
> > }
>
> I've tried that and it didn't work :(
> Maybe there's a problem on QtC side...
>
> Chris
> ___
> Qbs mailing list
> Qbs@qt-project.org
> https://lists.qt-project.org/listinfo/qbs
>
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
On Thu, 14 May 2020 at 23:34, Christian Gagneraud wrote: > > Hi there, > > As an experiment, i've just tried Qt-5.14, and this has enabled > multi-arch on Android. > I can select the list of architecture i want to support with > qbs.architectures. > This works for libraries, but my application is disabled: > Error while handling 'TestApp' > Product 'TestApp' had errors and was disabled. I've tracked the problem down into one library, I have an export item that seems to be problematic. For now i added an explicit dependency in the app, and removed the export. Looks weird... But now androiddeployqt fails with: Cannot find application binary TestApp Don't know why it's not one of the libTestApp.so, ... Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
Hi, are you using StaticLibrary or DynamicLibrary item for the libraries? Raph Le jeu. 14 mai 2020 à 13:34, Christian Gagneraud a écrit : > Hi there, > > As an experiment, i've just tried Qt-5.14, and this has enabled > multi-arch on Android. > I can select the list of architecture i want to support with > qbs.architectures. > This works for libraries, but my application is disabled: > Error while handling 'TestApp' > Product 'TestApp' had errors and was disabled. > > 3 of them, and that's all i get. I have 3 Depends that point to > internal libraries, maybe that's the smoking gun... > I have > multiplexByQbsProperties: ["architectures"] > qbs.architectures: ["arm64", "x86_64"] > For libs and apps. > I tried as well the 'usesNativeCode' but no success. > > Any idea what i'm missing? > > Thanks, > Chris > ___ > Qbs mailing list > Qbs@qt-project.org > https://lists.qt-project.org/listinfo/qbs > ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Android multiarch
> As an experiment, i've just tried Qt-5.14, and this has enabled > multi-arch on Android. > I can select the list of architecture i want to support with > qbs.architectures. > This works for libraries, but my application is disabled: > Error while handling 'TestApp' > Product 'TestApp' had errors and was disabled. > > 3 of them, and that's all i get. I have 3 Depends that point to > internal libraries, maybe that's the smoking gun... > I have > multiplexByQbsProperties: ["architectures"] > qbs.architectures: ["arm64", "x86_64"] > For libs and apps. > I tried as well the 'usesNativeCode' but no success. > > Any idea what i'm missing? Can you show us some more code or even a minimal example? ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
[Qbs] Android multiarch
Hi there, As an experiment, i've just tried Qt-5.14, and this has enabled multi-arch on Android. I can select the list of architecture i want to support with qbs.architectures. This works for libraries, but my application is disabled: Error while handling 'TestApp' Product 'TestApp' had errors and was disabled. 3 of them, and that's all i get. I have 3 Depends that point to internal libraries, maybe that's the smoking gun... I have multiplexByQbsProperties: ["architectures"] qbs.architectures: ["arm64", "x86_64"] For libs and apps. I tried as well the 'usesNativeCode' but no success. Any idea what i'm missing? Thanks, Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Signing an Android APK
On Mon, 11 May 2020 at 20:10, Christian Gagneraud wrote: > > n Mon, 11 May 2020 at 19:43, Raphael Cotty wrote: > > > > Hi, > > > > Release keystore support is not implemented yet: > > https://bugreports.qt.io/browse/QBS-1546 > > > > Can you explain a bit more 'jks' keystore type? > > It turned out that it's just a file extension, the file format is the same. > I'm now able to sign and run the APK from QtC, i just changed the > hard-coded values. > > I've commented on QBS-1546. I'll open a change request, changes are quite trivial. Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Qtc: Cannot find the androiddeploy Json file
On Tue, 12 May 2020 at 18:37, Richard Weickelt wrote:
>
>
> > When i want to "run" on the device:
> > Initializing deployment to Android device/simulator
> > Deploying to 150c980e8288de07
> > Cannot find the androiddeploy Json file.
> > Error while building/deploying project Neon Factory Tools (kit:
> > Android for arm64-v8a (Clang Qt 5.12.8 for Android ARM64-v8a))
> > When executing step "Deploy to Android device"
> >
> > I think this happens only when i do cosmetic changes in my qbs files.
> > The only way to recover is to trigger a manual build, changing a
> > source file is not enough.
> >
> > Any idea what's goind on?
> > Looks to me this problem is on QtC side.
>
> A quick guess and without ever having built an Android project: The selected
> product is the application executable and thus, none of the subsequent rules
> is executed. Could that explain it? Have a look at
> https://code.qt.io/cgit/qbs/qbs.git/tree/share/qbs/module-providers/Qt/templates/android_support.qbs
> There is a rule that produces qt_androiddeployqt_input (the json file) which
> I guess is not requested when you press the "run" button. There are also
> subsequent rules responsible for the deployment.
>
> You could add one of the rule's output to your product type, although I
> guess there is a cleaner way of doing it.
>
> YourAndroidProduct {
> type: base.concat("bundled_jar")
> }
I've tried that and it didn't work :(
Maybe there's a problem on QtC side...
Chris
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
