Trying to build QMsgPack lib for Android 6.2.0 Clang arm64-v8a
-
Following this -> https://qmsgpack.readthedocs.io/en/latest/install.html
at the bottom it states
Also you can just open qmsgpack.pro in Qt Creator and build it from there.and that's what i did!
This is the Compile Output
C:\AndroidSDK\ndk\21.3.6528147/toolchains/llvm/prebuilt/windows-x86_64/bin/../lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin\ld: cannot find -lqmsgpackd clang++: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [Makefile:69: libtst_streamtest_arm64-v8a.so] Error 1 make[2]: Leaving directory 'C:/build-qmsgpack-Android_Qt_6_2_0_Clang_arm64_v8a-Release/tests/stream' make[1]: *** [Makefile:47: sub-stream-make_first] Error 2 make[1]: Leaving directory 'C:/build-qmsgpack-Android_Qt_6_2_0_Clang_arm64_v8a-Release/tests' make: *** [Makefile:73: sub-tests-make_first] Error 2 15:48:55: The process "C:\AndroidSDK\ndk\21.3.6528147\prebuilt\windows-x86_64\bin\make.exe" exited with code 2. Error while building/deploying project qmsgpack (kit: Android Qt 6.2.0 Clang arm64-v8a) When executing step "Make" 15:48:55: Elapsed time: 00:06.now is there something i've missed or is there some error in the lib for Qt 6.2.0 or android?
-
Hi,
The last image suggest that you may be trying to use the version of QMsgPack that you built for a different architecture.
How did that file end up in that folder ?
-
Hi,
The last image suggest that you may be trying to use the version of QMsgPack that you built for a different architecture.
How did that file end up in that folder ?
-
Do out of source builds, so you can use it for all the target platforms you need.
-
Literally: "Do not build in the sources".
By default Qt Creator uses shadow builds which are out of source builds.
-
Literally: "Do not build in the sources".
By default Qt Creator uses shadow builds which are out of source builds.
-
On the contrary, keep it.
If you have already used it, then it's strange that building your application it looked for the library in the wrong place.
How are you pointing to it in your main project ?
-
On the contrary, keep it.
If you have already used it, then it's strange that building your application it looked for the library in the wrong place.
How are you pointing to it in your main project ?
-
There's an issue in the .pro file. It does not properly set dependencies so you might be building the tests before the library.
Either switch to cmake since Qt Creator also supports it or change the .pro file. See here.
-
No, modify the qmsgpack.pro file content.
-
No, modify the qmsgpack.pro file content.
-
I know, and that's the one you need to modify in order to ensure that src is built before tests following the instructions in the wiki I linked in my previous message.
The alternative is to comment out tests and the backslash after src but you won't have the tests built.
-
I know, and that's the one you need to modify in order to ensure that src is built before tests following the instructions in the wiki I linked in my previous message.
The alternative is to comment out tests and the backslash after src but you won't have the tests built.
-
Technically it ensures that the library is working properly if they run.
-
Did you also comment out the \ as suggested ?
